Recently a lot of my automations broke. It seems the "Actor" (object running the rules) all of a sudden did not have proper permissions. In the past I was not able to select what the Actor should be on a rule ("Automation for Jira", a User, Reporter, etc.) but now I can. I have "Atlassian-addons-project-access" on my permission schemes but "Automation for Jira" does not seem to fall in that bucket unfortunately. In fact, it seems I'll have to add the "Automation for Jira" object to ALL projects if I want to use automation.
Was there a recent release that changed this?
Aside from having largely shared permission schemes, is there an easier way to add this object to all project permissions?
This just happened for one of my teams' automations. The fix worked, but I can't find "Automation for Jira" as a user to update its permissions. How would I fix that?
Hey @[deleted],
Thanks for reaching out. There has indeed been some changes. I've posted about it here. Apologies for the delay on the post, I got a bit caught up in an incident.
In short, we're rolling out the ability to change the actor. However, we haven't changed it by default on you, so your rules should not have started failing on you. Rules that were running as our Automation for Jira user should have continued to run.
It sounds like someone might have changed the permissions which the Automation for Jira user is a part of? Or did users that you've changed the actor for start to fail?
Cheers,
Simeon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Simeon. I did not see any changes to permissions schemes or Actor on the automation. Perhaps I am missing something but I came in last week to 3 separate reports of broken automation on 3 different projects using 3 different schemes. I don't necessarily believe in coincidences.
Have you heard of other reports of similar behavior in the last week?
Is there something I can subscribe to in order to receive product release notes from Atlassian?
Much appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We had an incident towards the end of last week which could account for some of those errors.
At the time that they errored, were the actors still set to Automation for Jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share details on the incident? Is there a way I can sign up to be notified of incidents?
There have been no changes to the ACTOR of the automation rules in question in recent months.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @[deleted] , you can get details on this on our status page at https://status.automationforjira.com/
If the actor hasn't changed then this new feature won't have affected your rules. It can only kick in when the actor changes to someone other than our "Automation for Jira" user. I've also looked at the logs for your instance for the last week and I can't find any issues relating to this. It sounds like someone might have been fiddling with permissions.
If you've still got concerns about this, best to raise a support case.
Cheers,
Simeon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.