How to Create an Comment Alert in JIRA Automation Based on Status Summary field Updates?

[Jiri Masa]

Hello everyone,

I need some help with setting up an automation rule in JIRA. Here’s what I’m trying to achieve:

Goal:

• I want to create an alert by adding a comment to an issue if the "Status Summary" field has not been updated for more than a week.
• Alternatively, the alert should be triggered if there hasn't been a comment containing the text "status summary" added to the issue in the last week.

Context:

• Currently, we update the "Status Summary" field by adding a comment starting with "status summary."
• We need project managers to update this status summary every week, and this automation would greatly help us ensure compliance.

I’m not particular about whether the alert is based on the field not being updated or the comment not being added, as long as the reminder is triggered if either condition is met.

Could anyone guide me on how to set this up in JIRA Automation?

Thank you!

[Stephen_Lugton]

Hi @Jiri Masa ,

My initial thought is to add a new custom date field 'Status Summary Updated'.

Next create automation to detect when 'Status Summary' changes which sets now() to the 'Status Summary Updated' field.

You can also do the same for adding a comment containing 'Status Summary':

You can then create a scheduled automation rule that runs once a week and compares 'Status Summary Updated' to 7 days ago which then creates your comment on the issue.

[Stephen_Lugton]

Alternatively use Atlas and create a project corresponding to each epic and every Friday the owner of the project will get a reminder to give an update that will be sent round to anyone following the project on a Monday morning.

[Jiri Masa]

Thanks a lot, Stephen!

The problem is, I am not able to create custom field, most likely we will end up with weekly reminders :)

Or start updating already existing filed with count of days since last added comment by manager containing "status summary" and once it hits "7" add comment reminder

[Stephen_Lugton]

Your idea of using an already existing field would work