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

Way to automatically transit Jira issue status

User wants to have a function that can automatically transit issue status to next status when it's under a status for 5 days. For example, if an issue is Fixed for 5 days, then it can go to Closed automatically. I want to know if there's a way to do that.

1 answer

2 votes
Kristján Geir Mathiesen
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

Hi @Jason Liu 

You can use Automation to do that. The trigger is a schedule and the JQL could be something like:

status = "resolved" and updated < -5d

And the action is to transition the issue.

Let me know how it goes,

Hi KGM, it's a plug-in right? We don't have it in our system. But we have JSU automation and I saw that maybe we could create a trigger through it. I have another question. Do you know if the trigger has influence or pressure to the system? Since the trigger requires us to create a service. And the service will have a daily checking.

Hi again @Jason Liu  Automation is now part of Jira and Confluence but you might have to upgrade to a newer version. Not sure when it became integrated on Server.

I am sure the daily checking (i.e. the cadence, how often you run it) will affect performance of the server, yes. So you might not want to schedule heavy automation tasks to run too often.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events