I have a support project available to the enterprise where the only two groups who can view issues are the Support Admin Group and Reporters. The reason that this security is required is that reporters come from a variety of clients who should not see each other's issues due to client-confidentiality agreements.
The problem is that reporters would like to assign individual users as watchers to a ticket. The only way that I can see to do this is to create unique groups for each project and allow the reporters to change the security level on the ticket. This solution comes with unacceptable side effects: (1) it would be time-consuming and would become quickly inaccurate to maintain separate Sys Admin defined groups from Project Admin defined project membership (challenging), (2) Reporters would be able to view project-related groups across the enterprise (unacceptable).
Is there any other way to satisfy this request that I might be missing? A plug-in? Upgrade to JIRA 4.4 (we are currently running 4.3.4 and are in the process of an upgrade)?
This question is tangentially related to:
So actually the first thing you want to be able to do is let the reporter choose other people who have permission to view the issue.
Now reporters can add users to this field on create and edit, opening the issue to those extra users.
(This is actually what Atlassian does on support.atlassian.com with field called "CC")
Next you want to be able to add these users as watchers as well.
Sorry, my instructions only cover setting the Browse Project Permission, when it is likely that you are using Issue Security Levels.
You need to make sure that the users in the "Other Viewers" custom field not only have Browse Project permission, but also have permission to see the given Security Level.
If you want to find out why someone can't see an issue, and you are an admin, you can use the "Permission Helper":
Go to the issue, and choose "More > Permission Helper".
I believe this is built-in to JIRA 6.0 and higher.
For older versions, you can install a free plugin: https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-admin-helper-plugin
I've spent a lot of time playing with this issue, and at this time, I can't work out a simple solution. Either the watchers have to have permissions to "browse projects" which exposes everything, or they don't which locks down their ability to be added as watchers to an issue that they did not report. Creating a user's custom field that would then push to the watchers list, would require too much know-how on the part of our users.
That might work if your users were allowed to see all of the other users in the system. Ours can't, because our permissioning needs to happen at the project-scope level, meaning that users of one project do not need to know about users of another project, but both sets of users need to be able to log support requests in one uber-project, and, ideally, add specific watchers (likely from their own projects) to that ticket.
If a user could type in the username of the watcher in the Add watchers field and that user could be granted rights on that specific ticket, that would be great. Unfortunately, we haven't been able to provide that capability yet without, likely, eventual customization.
Sounds like you would need to create diffrent security groups per end customer group. That might help but that may be too much admin? But if you are talking about individuals that cannot be easily grouped, I don't see how you could grant them the ability to grant permission to another individual. Especialy if you don't want to allow users to see other users in the system.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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