JSM - Migration of legacy automations to the new format

[Dario Alarcón]

I am migrating some Legacy automations from a project and I find that they have a "time in status" trigger and can be parameterized with Days, Hours and Minutes.
Does anyone know how this trigger was replaced in the new Jira Service Management automations?
It works in the following way:
- If an issue is in a state for x amount of time, then the action is taken.

I understand that with the "Schedule" trigger I can do something similar, but it is not the same, since it would be executed at a certain time and what I need is for the time counter to be taken from the issue and not scheduled.
For example, when I transition an incident to a particular status and I need to receive a comment after 3 hours reminding me about this incident.

I hope you can help me, thank you very much!

[David Friedrich]

Hi @Dario Alarcón

in a JSM project you could set up an SLA that starts with the issue assuming the status. When the SLA gets breached or is about to be breached, this is your trigger.

To do this without an SLA, you could use a scheduled trigger and JQL to find the issues which have not changed status.

For example, this JQL finds any "in progress" issues which have not changed status in the last 24 hours.

project = myProject AND NOT status CHANGED AFTER -24h AND statusCategory = "In Progress"

[Dario Alarcón]

Hi @David Friedrich 

Thanks for your reply, but the problem I have with JQL is that it is executed on a scheduled basis and what I need is for the automation to be executed when the incident reaches a certain amount of time in a state.
That is, if the JQL is executed at 9 am and the 24 hours for the incident in a state have not yet been met, I must wait until the next execution so that it is taken into account in the JQL search.

[David Friedrich]

Hi @Dario Alarcón ,

yes, I get that. So actually the SLA approach is your only chance. Create an SLA and have your automation triggered by "SLA threshold breached".

OR set your Cron Job to check every ten minutes or so. AFAIK it only counts as an execution if issues were found and edited.