Automation Not Working When Story Has Restrictions

[Landin]

When I create a new story, if I add a restriction to it (e.g. only Administrators can view), automation rules do not get applied. Is there an additional rule I need to apply to have automation run on restricted stories?

BTW, I am running on a next-gen project.

Much appreciated!

[KAGITHALA BABU ANVESH · Accepted solution]

Hi @Landin ,

please check the below link.

https://blog.isostech.com/atlassian/automating-issue-security-with-automation-for-jira#:~:text=Go%20to%20Project%20Settings%20%3E%20%22Project,is%20created%22%20and%20click%20Save. 

[Mikhail Ponomarev]

Sorry I have the same issue, and I can't see how it is solved... No automation works if a ticket has any restriction! even if I am a part of a role to which the issue is restricted...

[Zhen GUO]

Try to add "rule" in Manage Workflow page.  And upload workflow, apply rules to all relevent issue types.  

[Zhen GUO]

hi there,  i would like to konw whether you solve the problem?

[brbojorque]

I believe you can choose who should be able to execute the automation.

Try adding your username in the automation settings and make sure that you have the appropriate permission to view/edit the issue aswell.

[Landin]

Are you referring to this setting? 

I am the admin of the project.  As mentioned before, the automation works if I don't apply restrictions to the issue, it is only when I apply restrictions that the automation does not trigger. Here is the restriction option I was referring to: