- I want to use Issue Security Level to manage Dev and QA who can/cannot see issue/task
- I created :
+2 group: TestDeveloper and TestQA
+2 roles: ProjectDeveloper and ProjectQA
+IssueScheme in Issue Security Schemes
- In IssueScheme,I add 2 security level: DeveloperLevel and QALevel
- In DeveloperLevel,I add ProjectDeveloper role
- In QALevel,I add ProjectQA role
- I assign IssueScheme into project
- I create an issue, choose Security Level => it just have "None" option (Expected: DeveloperLevel and QALevel must appear), but if in DeveloperLevel,I add Administrators roles(default role of JIRA).In QALevel,I add Developer role (default role of JIRA) then I create an issue,Security Level will have DeveloperLevel and QALevel options
> I create an issue, choose Security Level => it just have "None" option
That sounds like you have not associated the security scheme with the project. (Although you have got the "set security level" permission correct, which is the usual culprit for "I can't set a security level"). Please check the project security scheme.
I'm sorry, I do not understand. The "Issue scheme" is not the "security level scheme". In fact, it doesn't mean anything at all in Jira speak, which is why it is unclear to me.
The symptoms you describe, if I am understanding them correctly, are consistent with you not having set the "security level scheme" on the project.
Could you go to project administration and look in the "permissions" section. Copy and paste ALL the text there, so we can see what you have actually set up.
(Also, what do you mean "still works correctly"? Do you mean when you are part of one of those default roles, or do you mean when you use them in the security scheme?)
Here is my "project permission":
Project permissions allow you to control who can access your project, and what they can do, e.g. "Work on Issues". Access to individual issues is granted to people by issue permissions.
The problem is:
- If i set the groups/roles created by myself (like here):<th>Security Level</th><th>Users / Groups / Project Roles</th><th width="10%">Operations</th>
then I create an issue, Security Level just have "None" option
- But if I set the default groups/roles of JIRA (like here):<th>Security Level</th><th>Users / Groups / Project Roles</th><th width="10%">Operations</th>
then I created an issue, Security Level have "None", "ProjectDeveloper", "ProjectQA" options (it means my "it still works correctly")
I'll try and help.
Firstly in your Project's Permission scheme make sure you have the correct project role set up in 'Set Issue Security'. If you don't belong to a project role with that permission you can't set issue security.
If you've created an Issue Security Scheme which has security levels and you've created Security Levels associated with a Project role, that is good, you'll also have to associate it to your Project under Issue Security.
When you administer a project go to the 'Roles' section and ensure under the Project Role for 'ProjectQA' for example you've got the user group 'TestQA' for example assigned to that role.
The other thing you'll have to ensure is if the groups you've created are assigned as a single group to a user they'll need to have Global Permissions set as a JIRA user, or they won't be able to log into JIRA.
I hope you figured out the cause of the mentioned behaviour by now; so this answer is to help other JIRA users who are reading this because they are experiencing the same behaviour.
I the case you mention, you (and also the users setting the security level) have to be a member of 'Project Role (LogiGear_Developers)' to be able to set the security level to ProjectDeveloper. Likewise any user setting the security level to ProjectQA has to be a member of 'Project Role (LogiGear_QAs)'. It seems that a user cannot set the security level of an issue to a level the user cannot access. This is why you could set the security level when you changed the setup of the security levels to roles you had yourself.
This feature of JIRA prevents a user from setting the security level of an issue to a level where the issue cannot be accessed by the same user.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs