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 ...

Community
Q&A
Jira
Questions
How to have more than one security level per issue?

Add Watchers to a Next-Gen Project Jira Item/Epic

Hello,

A user can add themselves as a watcher to a particular Jira item in the current next-Gen Project (Cloud-based).

Any plans to allow a user to add another user as a watcher ?? This is supported is non-Next-Gen projects.

1 answer

1 accepted

1 vote

Answer accepted

Create a custom field (can be either a multi user or group custom field)
Open your security level
Use the custom field in the security level
Use this security level in the issue

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Add Watchers to a Next-Gen Project Jira Item/Epic

1 answer

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events