Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Run legacy automation rule as "Automation for Jira"?

Our former Jira admin has now left the company, and I've ended up being the new one. I have som probably simple questions. 

When using the legacy automation for auto-closing tickets can one change The "Run as" from the former admin to "Automation for Jira" or does it have to be a real user with some specific type of permissions? What's the best practice here?


Screenshot legacy automation.jpg

1 answer

0 votes
Mikael Sandberg Community Leader Aug 05, 2022

Hi @Matt H,

Welcome to Atlassian Community!

You should be able to run it as "Automation for Jira"

Screen Shot 2022-08-05 at 8.25.18 AM.png 

But my recommendation would be to not use legacy automation, instead you should try and convert them to the new automation instead. Some of the default legacy automations also exists in the new one, you can find those if you check out the Library.

Thanks for the quick and clear answer.

Sound like the easiest solution then is to initially set Run as user to "Automation for Jira" on Legacy Automation and start fixing the new automation rules.  



Like Mikael Sandberg likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events