nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation - Tigger "Create or Update" option?

siond

Hello!

I would like to know if a trigger exist which includes BOTH 'Create or update issue'.

So it will trigger if a subtask is created, OR if a subtask is updated? Right now I have to maintain 2 sets for automations for both scenarios!

Thanks

Accepted answers

All comments

Bill Sheboy

Hi @siond

No, there is no such trigger for automation rules.

If your rule maintenance is cumbersome, consider creating three rules:

Trigger on Create Issue, and make an update which can trigger rule #3
Trigger on Update Issue, and make an update which can trigger rule #3
Trigger on the condition created by rules #1 and 2, and perform the work necessary for both. For this rule to be triggered by other rules enable the "Allow Rule Trigger" option in the details.

Kind regards,
Bill

siond

Thanks Bill! Will give this a try!

Krzysztof Achinger

I stumbled upon similar problem where I wanted to run trigger Field value changed and then in subsequent if/else conditions check for whether the change in field value was during issue creation or update. I solved it by comparing dates for issue created vs. now. This could help in your use case @siond.

This condition will run when change was made during issue creation:

Screenshot 2023-05-18 at 17.17.12.png

You can verify that by logging action:

Screenshot 2023-05-18 at 17.17.25.png

Note: the solution does not guarantee 100% accuracy. If Jira slows down for some reason and fires the automation rule more than a second after issue was created, it may fail. So to prevent that you can further consider comparing the two timestamps (now and created) by calculating the difference between them and setting acceptable delay, e.g. 5000 milliseconds (5 seconds). Use {{[date1].diff([date2]).[unit]}} to do that. More documentation here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Bill Sheboy

Hi @Krzysztof Achinger

Such a rule could also run into problems when the automation engine is impacted, such as by an outage. In this case, some rules will run at an indeterminate time in the future and some will not run at all. (This has been confirmed by Atlassian staff in other community posts.) There really is no way to know/guarantee when a rule will run, and so relying on {{now}} to decide if a create or update happened could be problematic.