I have a context where 17 parties should not see issues of the others. I can manage that with issue security:
But how could I get something like: An issue arises that is in the intersection of 2 (or more) parties?
I don't see an easy solution here:
To make it clear: Normally, issues are separated by party, but at least for 30% of all issues, there is more than one party that should have access to it. And no, not all parties should be allowed to see these issues.
After some search ...
I have found the issue https://jira.atlassian.com/browse/JRA-14857where a (nebulous). There is the mentioning of one possible technique:
Another way to approach this would be to create a Multi-Group custom field and then change the Permission Scheme to be based on the custom field. This way issues can start off as being protected, but you can then add extra groups to the custom field, and allow the members of these groups to see the issues.
Does anyone know how this works? Perhaps this is a doable workaround ...
Depending on who has permission to edit the issue, users can then add users/groups into the custom field, thus granting them viewablitity of the issue. Or you could make a common transition specifically to edit that custom field.
Thank's a lot for the exact way how to do it. I have built a quick prototype configuration in an example project, which works like a charme. I only had to define the groups, and change the permission scheme so that the allowed groups may change the mapping.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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