Transition issues automation based on date

[Patrick Costello]

Hello.  For our business, when a partner exits we typically know in advance.  I want to set a date in an Exit Date field, then have an automation transition all outstanding issues to a completed status when that day hits.  I would like to do this to prevent agents from working those issues after our contract ends with the partner.
Is this possible?

There will be Epic issues and Child issues that need to be changed.

[Camilo Galleguillos · Accepted solution]

Hi, @Patrick Costello

Yes, what you describe is possible by setting-up a scheduled automation to run every day and checking via JQL if the current date is greater than the field's date. It would look something like this:

Here are more details on scheduled automation:
https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/

One important consideration here is the format in which the date is stored in your Exit Date field. More information on comparing dates:
https://support.atlassian.com/automation/kb/comparing-issue-dates-in-jira-automation/

Hope this information is helpful.

Camilo Galleguillos Sr. Technical Consultant ServiceRocket camilo.galleguillos@servicerocket.com Santiago, Chile

[Patrick Costello]

That is helpful, thank you.
If the automation runs once a day, is it just one automation? Does it add up all the issues it transitioned and count them? or does it count for every issue it checks? (We have about 70K issues)

I just don't want to run out of my limited amount of automations

[Tomislav Tobijas _Koios_ · Accepted solution]

Hi @Patrick Costello ,

Quick answer regarding the following:

If the automation runs once a day, is it just one automation? Does it add up all the issues it transitioned and count them? or does it count for every issue it checks? (We have about 70K issues)

Short answer is yes - even if your rule performs actions on multiple issues, it's still counted as one rule execution.

However, a note is that automation rules have specific service limits. In this specific case, going through 70k issues and performing actions on each will most likely take more than 70 executions as searching/actions performed within one rule can be done up to 1000 issues.

Recommended way to avoid this is to change the automation rule scope - whether by setting the scope in rule details, or just by adjusting filters (JQL) used within triggers, branches or actions.

Cheers and happy new year,
Tobi