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

Add public comment if the ticket is in particular status for 5 days


If the status is Awaiting for Customer for 5 days and the ticket is not updated for 5 days. Then add a public comment on the issue.

I hope this is possible in Jira.. Please help me to achieve this.

I have added a rule using Automation for jira unfortunately it didn't worked for me. I have attached screenshot for your reference.


MadhuAutomation for Jira.png

1 comment

You need to use a different trigger. The trigger you are using only takes action when the issue is initially transitioned.

You want to use the "scheduled" trigger. This is a trigger that occurs at a regularly schedule time periodically.

You can set this trigger to run once a day, for example. Then once a day it will evaluate all the issues and if any match, will take the action n them. 

Like Madhu Reddy likes this

Hi @Andrew Laden , Thanks for the help.

I have changed the trigger as below and still I am not able to get the expected results.

Can you please correct me if I was wrong..

For test purpose I have changed the time to 5m.



MadhuScheduled Trigger 1.pngScheduled Trigger 2.png

Hi @Andrew Laden ,

I got the point that changing the trigger is the resolution but here it is not acting according to the JQL query.

I have added JQL query that If the ticket is in Particular status and not updated for -5m.


But the rule is neglecting the Second part of the query and Picking all the tickets in that particular statuses. ( Any way we can manage this by using Use this rule since the last time executed check box ) it an expected behavior.


It will be good if it consider the Second part of the JQL last Updated part.



When you click on "Validate Query" it should show you all the issue that match your current query. You can use that to fix your JQL. Make sure that it only shows the issues you would expect to see.

Also, you probably want to uncheck the "Only include issues that have changed since last time this rule executed" and that is the exact opposite of what you want.


Log in or Sign up to comment