My initial thoughts are:
- two automations: one for adding label, one for removing
- think about the scope of this automation. it sounds like the most suitable trigger is a scheduled daily run. You will need a JQL for that to look at tickets that are in to-do and in-progress status groups. You may want to tighten it to look at a specific issue type or a space if needed
- your jql should look at due date vs today
- your jql should exclude already overdue items
- add 'Overdue' label to whatever is returned by jql
- consider adding a comment like 'Issue is now overdue'
- second automation should be triggered when transitioning to a 'Done' status group and remove the 'Overdue' label
Consider that if you ever want to report on Overdue tickets, the easiest way would be to look for that label, and therefore you might want to consider keeping it.
Here's the proposed jql based on the above. I would consider adding issue types or spaces if that matters:
statusCategory NOT IN (Done) and duedate < startOfDay() and labels NOT IN (Overdue)
1st automation:
- Scheduled trigger executing daily before opening hours (maybe after midnight)
- IF Condition - JQL based using jql above
- THEN - Edit Issue - Labels: Choose ADD/REMOVE and specify 'Overdue' in the Add section
2nd automation if you decide not keep the label after resolving the ticket:
- Trigger on 'Work Item Transitioned' to whatever your Done status is, could me multiple depending on how many issue types your JQL grabs
- IF Condition - JQL labels IN (Overdue)
- THEN - Edit Issue - Labels: Choose ADD/REMOVE and specify 'Overdue' in the Remove section
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.