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

When a user is administrator of an organization, he should be able to manage the users of this organization (enable / disable) #8011

Closed
SamuelHassine opened this issue Aug 11, 2024 · 2 comments · Fixed by #8030
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)

Comments

@SamuelHassine
Copy link
Member

Description

  1. Promote a user as admin of an organization
  2. Login as this user
  3. Try to disable a user part of the organization

=> It should be possible, it is not.

@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Aug 11, 2024
@nino-filigran
Copy link

nino-filigran commented Aug 12, 2024

The behavior happens when:

  • user is org admin only (not settings capa on its role whatesoever)
  • user tries to disable a user by changing its account status

@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 Aug 12, 2024
@romain-filigran
Copy link
Member

Reproduced. Exception "Cannot read properties of undefined (reading 'find')" when updating account status.
Capture d'écran 2024-08-12 092245

@nino-filigran nino-filigran removed the needs more info Intel needed about the use case label Aug 12, 2024
@romain-filigran romain-filigran added this to the Bugs backlog milestone Aug 12, 2024
@Kedae Kedae added the regression Label to identify the bug as a regression of previously working feature label Aug 12, 2024
@marieflorescontact marieflorescontact self-assigned this Aug 14, 2024
marieflorescontact added a commit that referenced this issue Aug 16, 2024
marieflorescontact added a commit that referenced this issue Aug 16, 2024
marieflorescontact added a commit that referenced this issue Aug 22, 2024
marieflorescontact added a commit that referenced this issue Aug 22, 2024
marieflorescontact added a commit that referenced this issue Aug 23, 2024
marieflorescontact added a commit that referenced this issue Aug 23, 2024
marieflorescontact added a commit that referenced this issue Aug 23, 2024
marieflorescontact added a commit that referenced this issue Aug 23, 2024
marieflorescontact added a commit that referenced this issue Aug 27, 2024
marieflorescontact added a commit that referenced this issue Aug 27, 2024
@marieflorescontact marieflorescontact added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 30, 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)
Projects
None yet
5 participants