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; } } }

Is it possible to have multiple automation rules with same action but different trigger?

kana.okuma

We are trying to create an automation rule in our service management project.

The triggers we are trying to use are 1. when issue is created 2. when issue status is changed from done to in progress.

I tried setting multiple issue events for the trigger but could not specify the transition so I guess that doesn't work in this case.

Would it be better to have multiple automation rules with the same action but different triggers? or is there a workaround for this.

Accepted answers

Walter Buggenhout

Hi @kana_okuma and welcome to the Community!

Yes, sure. The trigger is what makes your automation rule fire. If only for clarity, it might be best to create different rules when they are triggered though different events, even if they perform the same actions.

You can copy an automation rule and then update the trigger of your copied rule to avoid having to rebuild all the steps manually.

Hope this helps!

All comments

Walter Buggenhout

Hi @kana_okuma and welcome to the Community!

You can copy an automation rule and then update the trigger of your copied rule to avoid having to rebuild all the steps manually.

Hope this helps!

kana.okuma

Hi @Walter Buggenhout

Thank you!

Will try setting up different rules for this case.

Aron Gombas _Midori_

@kana_okuma Let me mention an opportunity to eventually "merge" rules with different triggers. If you can combine the multiple "triggers" to the same JQL search, then you can use a single rule with the "periodic" trigger and with that JQL.

For your use case you could use a JQL similar to this:

created > now("-10m") or status changed > now("-10")

Of course, if your rule runs more frequently than 10 minutes, it will find the same work item multiple times. To avoid that, you can change your rule to add a "marker" label "Processed" and also test for that label.

(created > now("-10m") or status changed > now("-10")) and label != "Processed"

You probably get the idea.

If you have a large number of almost-identical rules, it can be a considerable approach. For just two rules, maybe the redundancy is fine.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management