Automation to add a filter to unresolved issues

[Colum McAndrew]

I'm looking for a way to automatically add a label to issues that have been stuck in a particular status for a period of time. Most of the automation events seem to rely on something happening for the automation to work (e.g. a status change, comment added, etc.). What I want is the opposite, automation when nothing happens to an issue.

The only way I can see this working is by using the Scheduled automation task to run a JQL query, and use the Edit Issue condition to add the required label to all the issues returned by the query.

Does this sound like a good plan?

[Hana Kučerová · Accepted solution]

Hi @Colum McAndrew ,

yes, I think this is a good plan. We did very similar thing.

[Colum McAndrew]

Thank you Hana. I'll test this with a scheduled task to run tomorrow AM. If this works it should really help my teams integration metrics with Tasktop.

[Hana Kučerová]

If something goes wrong, please, let me know, I will try to help.

[Colum McAndrew]

Hi @Hana Kučerová The concept seems to work, but the JQL query required is missing one vital piece.

I ran a test using some dummy JQL to see if the idea worked, and it did. However the actual JQL required needs to include issues with a particular status, but only those that have remained in that status for more than two weeks.

It is that last element that I can't seem to find the right parameter for. There doesn't seem to be anything to report on this (e.g. a status change date). There is the UpdatedDate, but this could be triggered by anything.

Any ideas?

[Hana Kučerová]

Hi @Colum McAndrew ,

originally I used JQL:

status changed to XXX BEFORE YYY

But this wasn't working correctly, because in our case issue could get to status XXX repeateadly.

So, I ended up creating new Date custom field, where I store the date, when the issue was transitioned to status XXX for the last time. Then I use this custom field in the automation rule.