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

EE button in organization edition is not clickable #6378

Closed
Archidoit opened this issue Mar 18, 2024 · 4 comments · Fixed by #6410
Closed

EE button in organization edition is not clickable #6378

Archidoit opened this issue Mar 18, 2024 · 4 comments · Fixed by #6410
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Archidoit
Copy link
Member

Reproductible steps

Disable EE.
Go to Parameters > Settings > Organization.
Go to an organization overview.
Edit it.
The EE button next to the 'granable groups' field is not clikable whereas other EE button in the platform are.
image

When we click on the EE button, a pop-up should open, enabling to activate EE.

@Archidoit Archidoit added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 18, 2024
@Archidoit
Copy link
Member Author

In the user edition form, the EE button next to 'Organization admin' is not vertically aligned (it is too low) :
image

@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 20, 2024
@nino-filigran
Copy link

@Archidoit I cannot reproduce on Testing. Does it still happen on your side?

@nino-filigran nino-filigran added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 20, 2024
@Kedae Kedae removed this from the Release 6.0.8 milestone Mar 20, 2024
@Archidoit
Copy link
Member Author

@nino-filigran I still reproduce it on testing

@nino-filigran
Copy link

My bad, for whatever reason, I guess it did work for a bit. I've also tried again and got same result as you do.

@nino-filigran nino-filigran removed the needs more info Intel needed about the use case label Mar 20, 2024
@SarahBocognano SarahBocognano self-assigned this Mar 20, 2024
@Kedae Kedae modified the milestones: Release 6.0.8, Release 6.0.9 Mar 22, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 3, 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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants