The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to setup a an automation rule to set a custom field for overdue

Jürgen Wieser
Contributor
November 11, 2024

Can anybody help with my following problem:

I want to detect any overdue issue (not only as of now but also to record for future statistics).

Since I am not able to compare the duedate field against date status changed from X to resolved, I would like to set a custom filed if an issue runs overdue.

For that I have

1. created  a custom field Overdue (option Yes, No)

2. created an automation rule as following

image.png

The rule builder says:

image.png

How do I have to setup the suggested for each branch?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Dick
Community Champion
November 11, 2024

Hi @Jürgen Wieser , 

An automation always needs to know on which issues it needs to work. This is not the case in your situation. The rule builder tells you to adjust your automation with the for each branch. 

This branch can be adorned by JQL like: Project = "XYZ" and status != Done to yield the issues you would like to be (potentially) changed by the automation. 

It is wise to run this schedule between non-office hours as the for each statement could demand a bit of time to be executed in case of a very active project with many issues.

Try it, you will like it.

Dick

DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events