You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The list of project-specific roles in the Project Settings page only seems to show 1 role, even if other roles should be shown. It can also incorrectly show roles if they used to be specific to a project in the past.
Steps To Reproduce
Create two roles
Give one role Project Admin permissions to any project
Go to Project Settings > Permissions > Roles, and validate that that role is present
Give the other role Project Admin permissions to the same project
Go to the project roles page again - only the role from step 2 will be shown
If you remove Project Admin permissions from the first role, it will still be shown incorrectly in the project roles page.
If you delete the first role, the second role will now be shown correctly in the project roles page.
The endpoint returning incorrect data is GET /api/v1/organisations/15467/roles/717/projects-permissions/?project=22470
Expected behavior
All project roles should be returned in the project settings page.
Screenshots
project.roles.mov
The text was updated successfully, but these errors were encountered:
How are you running Flagsmith
Describe the bug
The list of project-specific roles in the Project Settings page only seems to show 1 role, even if other roles should be shown. It can also incorrectly show roles if they used to be specific to a project in the past.
Steps To Reproduce
If you remove Project Admin permissions from the first role, it will still be shown incorrectly in the project roles page.
If you delete the first role, the second role will now be shown correctly in the project roles page.
The endpoint returning incorrect data is
GET /api/v1/organisations/15467/roles/717/projects-permissions/?project=22470
Expected behavior
All project roles should be returned in the project settings page.
Screenshots
project.roles.mov
The text was updated successfully, but these errors were encountered: