You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
JQL
Also,
Here's a snapshot of the automation.
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?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suspect the automation rule is triggering on something else and not the Updated date itself then. But I can't answer that or tell you what constitutes an issue being "updated". I can just a solution based on the observances you describe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeah that did work! just a little confusing what is constituted as an update. Guess there is a distinction between comment and issue update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, to me adding a comment should constitute an update as well. But glad that worked for you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.