We have an automation job (in the legacy automation section) that changes the state of resolved tickets to closed after 3 days. Unfortunately the user who the job runs as has left and I'd like (ideally) to change the job so that it runs as an account that's not linked to an actual user.
When I click on the gear icon to update the 'Run rule as' value the drop down says:
This option cannot be selected because one of your WHEN statements cannot be run as the user who triggered this rule.
Is there a way to update this value in the legacy rule (as at some point we're going to need to remove the user who's left) or do I need to implement this as a 'normal' automation rule?
In legacy automation there are only 2 options in "Run rule as" drop down. 1. Project default -- which takes from project lead value. 2. Run as user triggered.
Which option is selected in your case?, give a try by changing the project lead value.
I would recommend to move over to normal automation rule which offers flexibility of actor option. Ideally "Automation for Jira" user can be given as actor or users from user management.
Hi Colin - Welcome to the Atlassian Community!
I guess one option is to give the new person the same permissions as the one who is leaving and then switch it to them.
Otherwise, you will need to implement it as a new automation rule and let Automation for Jira be the actor.
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
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