I'm having a struggle in doing the following: Goal: If an issue is just updated and is not resolve and closed and due date is in the past add a comment. Issue: * I have this kinda working but only triggers if the due date is changed* but I'd like it to trigger whenever the issue is updated and it meets the overdue criteria * It shows in the audit log that the rule didn't run * what am I doing wrong?? JQL * status != closed and status != Resolved and due < startOfDay() and due is not EMPTY Also, * I have "Prevent duplicates by only adding this comment once to a particular issue." disabled. Here's a snapshot of the automation.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jira - project automation - add comment if issue is updated and due date has passed when updated

Gavin_b342qo

I'm having a struggle in doing the following:

Goal:

If an issue is just updated and is not resolve and closed and due date is in the past add a comment.

Issue:

I have this kinda working but only triggers if the due date is changed
- but I'd like it to trigger whenever the issue is updated and it meets the overdue criteria
It shows in the audit log that the rule didn't run
what am I doing wrong??

JQL

status != closed and status != Resolved and due < startOfDay() and due is not EMPTY

Also,

I have "Prevent duplicates by only adding this comment once to a particular issue." disabled.

Here's a snapshot of the automation.

Accepted answers

John Funk

Hi Gavin,

What did you change that should have updated the issue? And what that change done directly to the issue? Or was it a change to the issue as the result of another rule running that updated the issue?

All comments

John Funk

Hi Gavin,

What did you change that should have updated the issue? And what that change done directly to the issue? Or was it a change to the issue as the result of another rule running that updated the issue?

Gavin_b342qo

Thanks for the response.

What did you change that should have updated the issue?

> I added a comment

And what that change done directly to the issue?

> yes

Or was it a change to the issue as the result of another rule running that updated the issue?

> no

John Funk

So, that tells me that adding a comment to an issue does amount to "updating" it in Jira's eyes. You would need a second rule that handles those - you should be able to simply copy your existing rule and change the Trigger to Comment added instead of Issue Updated.

Gavin_b342qo

So does that mean that comment added isn't an issue update? If so why does the "updated" field show the last comment that was add time time stamp?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server