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

Can I add multiple trigger(manual, issue create) in one automation rule

Masudur Rahman_drdg74

Hello,

I have one "Manual Trigger" automation rule. I want to add more trigger such as "issue created", "issue updated", etc as well.

How can I do that? Currently I'm seeing only one trigger(either manual or issue created and or issue updated etc). But I want both manual trigger and issue created trigger execute this automation rule.

Note - I can copy the rule and change trigger to issue created or updated but in that case every time required changes I'l have to do manually update both the rule(s), I want to avoid that.

Thanks
Masud

Accepted answers

Andy Heinzer

Hi Masud,

I understand that you're using the Automation for Jira Server plugin to create some rules, and that you want to be able to create a rule that has both multiple triggers and a manual trigger.

This is not something that can currently be done with the Automation for Jira Server add-on in the current versions. The manual trigger run is not designed to have other possible triggers. Its intention is to let you choose when to run an automation rule and not to have it be based on a process or workflow step to trigger the rule. More details on that rule can be found in Manually run a rule against an issue.

I suspect that this is done by design. In my view the Manual trigger is not technically an issue event in the same way that issue created, issue edited, issue closed, etc are. That said, I do agree that this would be useful to have. So I created a feature request for this over in JIRAAUTOSERVER-14.

In the meantime, the best I can seem to do is to first create the multiple issue event trigger rule, then copy it, and in the copied one edit the trigger to just be manual. I know that isn't an ideal workaround as it creates an extra rule to manage, but at least it might help to give you the immediate functionality desired.

I hope this helps.

Andy

All comments

Andy Heinzer

Hi Masud,

I understand that you're using the Automation for Jira Server plugin to create some rules, and that you want to be able to create a rule that has both multiple triggers and a manual trigger.

I hope this helps.

Andy

Masudur Rahman_drdg74

Hi @Andy

Thanks.

Martin Cleaver

Looks like there is no progress on this, but I concur - I've often wanted this. Managing rules is hard enough without having partial duplicates.

Puja Verma

Yes, not able to add multiple triggers is a problem. As a workaround, we did something that may work for you -

Keep the common logic in one rule which can be triggered through a webhook (using webhook trigger)
Then create other rules (as many as the number of triggers needed), all invoking the same rule created in the first step through its URL.

Miguel Fernandez_lcu1uu

+1 This would be amazing to have.

Danielle Harder

+ 1 Would like to have this capability to have more than 1 trigger in a single rule. Would like to automatically duplicate primary task fields in generated sub tasks from a primary task automation that is initiated manually.

hadesunseenn

Yep we need to trigger the webhook for comment Add/Edit/update. Now we will have to add 3 different automation

Daniel Alomar Claramonte

The multiple issue events is the solution:

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Automationtriggers-Multipleissueevents

Mike Anderson_vxit50

Solved for creating manual and field change triggers

I had the same issue: I have a Rule that triggers off a field change (Field1) and I wanted to be able to run this rule manually as well.

I created the rule (Rule1) to run off the change first. I made it recursive by checking the box in the Rules Details page next to: Check to allow other rule actions ....

Then I created another rule (Rule2) that is manual trigger. It

Saves the current issue's field 1 {{issue.Field1}} to a variable ({{var}})
Then changes the current issue field 1 to nothing/blank
Then changes the current issue field 1 to the saved variable {{var}}

Basically it tricks the rule trigger by setting the target field to blank, then setting it back to it's original value.

good luck

Mark Caldwell

Genius. Thanks. Using this approach.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

automation