The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Overview:
Ask
@Gavin I think you need to rethink your process. If the process is so complex that it requires a workaround on your security policy you should be looking to simplify it or change it so it supports your security model. What issue are you having that you have to remove security to perform an action in Jira?
Overview
- item 1 - Group A - Can view the issue
- item 2 - Group B - Can not view the issue
- item 3 - Group A - can add a member of Group B to the watcher field allow them to view the issue.
current scheme: Level 1 Security Level
Issue:
- when group A member adds a Group B member into the watchers field.
Error:
here was an error adding watcher
Observations
How can I add Group B member into the watchers list so that they can view the issue without removing the level 1 security level?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gavin The issue is the fact that you are using the watcher field. There are several enhancement requests that ask for watcher field to be utilized in the manner that you are asking but have not moved forward yet. You can easily create a multiselect user picker custom filed to your project and add individuals that way. It is supported and will not require you to change the issue security to add individuals.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.