Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

jira - automation - security policy assigned


  • I have a jira issue with a security policy assigned to it.
    • some users change the security policy to NONE because due to the security policy some changes can't occur under that.
    • they don't add the policy back
  • yes I know not ideal but it's a more complicated situation than shared above.



  • is there a way to run a workflow automation that
    • can you put a delay in the automation to run after an issue has been updated for example 2 minutes? 
  • I know you can run it every 2 minutes but that is overhead not needed as I only want it to occur when an issue is updated.

1 answer

1 vote
Brant Schroeder Community Leader Jun 14, 2022

@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?  


- 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 

  • Current assignee
  • Group (Group A)
  • Project Role (Administrators)
  • Project lead
  • Reporter



- when group A member adds a Group B member into the watchers field.


here was an error adding watcher

  • The user "groupUserBmember" does not have permission to view this issue. This user will not be added to the watch list.



  • if we remove the security level (clearly it'll work)
    • add GroupB Member to watchers
    • then apply the level 1 scheme
    • it works

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?

Brant Schroeder Community Leader Jun 16, 2022

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

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you