I have a context where 17 parties should not see issues of the others. I can manage that with issue security:
- Create an issue security scheme
- Create a security level per party
- Define for each created issue the security level
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:
- Define for each intersection a separate security level (which is an administrative burdon)
- Anything else?
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.
Any idea?
----
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 ...