After upgrading JIRA from Version 4.3.4 to JIRA 5.1.1 we have noticed, that we have a problem with the Issue Security Scheme. We noticed it when filters didn't show any issues although the affected users do have viewer and worker rights on the project and Issue Security is set properly by a Group Custom Field Value. It worked smoothly before the upgrade and we didn't change any configuration setting afterwards.
We already raised an issue: https://jira.atlassian.com/browse/JRA-29196 and got the answer if we need a bugfix INSTANTLY, we need to open an issue here.
More detailed bug description:
The security level of the issues is configurerd with a specific Issue Security Scheme. The Customer Security Level is set with a Group Custom Field Value. In our case we use the content of a field named Bank Unit. Bank Unit is a Custom Field of type Select List.
All values of that select list are group names too (e.g. Value of Bank Unit: Bank xy and group name of the group to which the user belongs: Bank xy).
Issue security works fine with direct URLs. A user can access issues, when he is in the group mentioned in the field Bank Unit and he is blocked, when he is not in that group.
All filters/queries return zero – even if we use a very simple search criteria like project = Project A
Did you get resolution for this request.
This is a strange problem .
For security It is checking for custom field option names. But for Permission it is looking for Custom field Option id.
Ex : There is custom field A with Options "Option1" and "Option2". As we know for each option some ID will be associated, assume for Option1 the ID is 1234 and for Option2 the ID is 2345.
To access jira tickets where customfield A value is Option1, you have to create two groups. one is Option1 and second one is 1234.
if you are part of Option1 , you can view the ticket and if you are part of 1234, you can get it in issue navigator.
we never got a resolution for our request. Fortunatly we found a workaround too, but we are using a self-written plugin for that. It offers a post function that copies the Select List option value to a Group Custom Field. We changed the Issue Security Scheme to use that field.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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