-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.0.2, 6.0.6
-
6
-
Here is the step to reproduce the issue:
- Install a fresh JIRA 6 instance.
- Create a second "user1@test" then rename it to "user1".
- Create a new issue security scheme with one security level limited to admin user and "user1".
- Create a new project and one issue with the security level.
- Logout and login with the account "user1" then open the issue.
- The Permission violation page shows up.
Please note that the issue only affected the security level or project permission created after user renamed.
As a temporary workaround solution: It is possible to create a customfield with type of user picker and associate with the issue security / project permission, then add the user name in the customfield. As only the user who got the edit issue permission can edit the field.
- is cloned from
-
JDEV-23962 Failed to load
- mentioned in
-
Wiki Page Failed to load