Automating "in progress" notifications and Rovo for troubleshooting

[#1]

Hey all,

Below is some Q&A and follow up on a live session I did on August 21st on Jira Automations. This is one of the several courses we offer over on the Public Classes in atlassian learning (check them out - most are free!).

Question 1 - Is it possible to set up notifications to notify the assignee of a ticket that has been "in progress" for over a week?

• Answer - Yes. Using a JQL condition similar to the following will pull up all the tickets that haven't changed status.

• statusChangedTo("In Progress") <= -7d (or status = "In Progress" AND 
  statusCategoryChangedDate <= -7d) 

• then adding an action to send a notification or comment.

• Here's a Rovo prompt I used to help make that : "create an automation that will comment on any ticket that has been in the “in progress” status for a week or longer".

• One thing to consider here is if it's a bad thing for a ticket to be "in progress" for a week. e.g. are there legitimate reasons for it to be in that status vs. another one? Or, are there other conditions that would indicate it's OK for it to be in that status?

Question 2 - Can Rovo help us fix any existing automation rule if it fails?

• Answer - Kind of? Rovo can't edit or fix an automation from the Space... it can however copy the error message or audit log details from the failed automation rule and paste it into Rovo. Rovo will analyze the error log, explain what the error means, and provide specific recommendations on how to troubleshoot and resolve the rule logic or field configuration.

• Keep an eye on this one... Rovo is being updated all the time, so I wouldn't be surprised if this changes in the near future.

[MahanthPrudhvi]

@Rob Hean Thanks for sharing this! One question regarding the JQL:

If an issue was In Progress for several days, then moved to another status, and later moved back to In Progress, would statusChangedTo("In Progress") <= -7d still return that issue based on its earlier transition?

For example:

Aug 1: To Do → In Progress
Aug 5: In Progress → Testing
Aug 10: Testing → In Progress

Would the issue be considered as having been In Progress for 7+ days, even though it has only been continuously In Progress since Aug 10?

Similarly, does statusCategoryChangedDate have the same limitation when the statuses belong to the same status category?

I'm trying to understand how to ensure the notification only triggers when an issue has been continuously in the exact In Progress status for 7+ days.