-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Medium
-
10
-
Severity 3 - Minor
Issue Summary
Permissions can be assigned directly to users. In Jira, user records have two different attributes, user key and username. The bug happens when a user has two different records, as exemplified below:
| User Id | User Key | Username |
|---|---|---|
| 1 | A | B |
| 2 | B | C |
When user 1 is referenced in a permission scheme, Jira will display user 2's display name. In case there is no record for user 2, Jira will display user 1's key.
Steps to Reproduce
- Access a permission scheme
- Grant a permission to a single user
- Here, the problem will only occur if the user once had a record that was deactivated and is currently pointed as Former user or if there exists a user record that once
Expected Results
Correct user is displayed
Actual Results
Incorrect user record is displayed:
Additional Information
Although Jira displays the permission as being granted to a Former User, the permission is properly associated with the correct user in the database, so this behavior does not represent a permission problem.
Workaround
This problem is not reproduced if the permission scheme is accessed through the project settings page (Project Settings > Permissions).
- is related to
-
JRACLOUD-71467 Editing the value of user picker custom fields results in an error if the user had their user_name changed.
-
- Closed
-
- mentioned in
-
Page Loading...