[go: nahoru, domu]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Authorized Member in the customization of a Feedback #7151

Closed
nino-filigran opened this issue May 28, 2024 · 0 comments · Fixed by #7170
Closed

No Authorized Member in the customization of a Feedback #7151

nino-filigran opened this issue May 28, 2024 · 0 comments · Fixed by #7170
Assignees
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR) ui for scope limited to UI change
Milestone

Comments

@nino-filigran
Copy link

Description

Feedback supports the concept of Authorized Members. It seems that the functionality to define default Authorized Members has disappeared from the customization panel of the Feedback.

Environment

All

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to parameters
  2. Go to customization
  3. Go to feedback

Expected Output

In the list of fields that you can set up default values for, there should be the authorized members.
When clicking on it, it should open the popover of authorized members (the one in the dashboards, image below) and you can select default sharing members.

Actual Output

The field is not there.

Additional information

Screenshots (optional)

image

image

@nino-filigran nino-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels May 28, 2024
@nino-filigran nino-filigran added this to the Bugs backlog milestone May 28, 2024
@CelineSebe CelineSebe self-assigned this May 28, 2024
CelineSebe added a commit that referenced this issue May 29, 2024
Signed-off-by: Celine Sebe <celine.sebe@filigran.io>
@CelineSebe CelineSebe linked a pull request May 29, 2024 that will close this issue
5 tasks
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 29, 2024
@Jipegien Jipegien added regression Label to identify the bug as a regression of previously working feature ui for scope limited to UI change labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR) ui for scope limited to UI change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants