Automation Not Working When Story Has Restrictions - new

[Mikhail Ponomarev]

When issue has any restriction, no Automaton works (Jira Software, next-gen)

[Nic Brough -Adaptavist-]

Thanks @Mikael Sandberg - reading back, I've been assuming we were talking "administrator role in the project", but I had not said it clearly.

[Mikael Sandberg]

Since you are using a team-managed project you have to make sure you have role of Administrator in the project that the automation is running, which is different from being a Jira admin.

[Nic Brough -Adaptavist-]

I'd want to see that you are in the role of administrator for the project as a last screenshot for support, but the rest of your screenshots are telling me that there is a bug (possibly a couple)

Working from the bottom upwards:

• The Automation actor is you in the last screenshot
• The error message is clear in that it thinks that actor cannot see the issue
• The next error up (in the light red box) is useless in telling us what is wrong (possible bug there)
• The restriction is to people in the role of administrators

So there's only three things left we don't have a screenshot of:

• You are not an administrator
• The issue has been deleted between the screenshot you took of the restriction, and the next run of the automation (no need to screenshot, we all know it's still there - you can see it!)
• There's a bug in Automation, probably that it is not recognising you as an administrator who should be able to see the issue

I think this one needs to go to Atlassian!

[Mikhail Ponomarev]

"I think this one needs to go to Atlassian!"

That's what I'm afraid as well... Asked our IT Support to reach out to them... :( 

[Mikhail Ponomarev]

I do have a role of Administrator in the project that the automation is running, that's the whole point! Jira's admin's are our IT team. 

If I wasn't Administrator of the project I would not be able to view issue from which I made screenshots, because it is restricted to Administrator.

[Mikhail Ponomarev]

Automation for Jira - seems to be what you mean by "account that runs the automation matters"... May be it has wrong settings as account? Because I can't add it to the Project and therefore I can't add it to Restrictions....

[Mikhail Ponomarev]

When issue is restricted:

Where I am the Administrator, NO automation work. None at all.

First of all, if I check here in the issue:

I see this weird ERROR:

 

Second, when I try to trigger Automation rule, the Audit Log of the rule shows me this failure error:

Which is a false statement! Issue is not deleted and I have permission to view the issue (see above - I am the Administrator).

You may think that I also have to restrict issue to Automation for Jira. I don't think that's needed. In my Automation rule - I have changed Actor to myself! So I don't think "Actor" is a problem here....

Hope this explains! 

[Nic Brough -Adaptavist-]

Ok, so you'll need to show us the automation, the "restriction" and what it is doing.

[Mikhail Ponomarev]

Not helping… in my automation rules “actor” is me and I am the one to whom issues are restricted…. 

[Nic Brough -Adaptavist-]

Automations respect the restrictions on issues, so check who the "Automation user" is - the account that runs the automation matters.  You'll need to include them in the "restriction" (I'm not sure what you mean by that though - project visibility?  Project permissions? Issue security?  Workflow conditions?)

[Mikhail Ponomarev]

This similar discussion DOES NOT solve the issue for me...

https://community.atlassian.com/t5/Jira-Software-questions/Automation-Not-Working-When-Story-Has-Restrictions/qaq-p/1586494