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 there a way to manually trigger an automation against multiple issuse?

Jeff P_1irk0f

We are using Jira DC-9.12 and we need to trigger automation on multiple issues at the same time. We update a %complete field in AR but AR won't trigger our automation that updates the project estimates, so we need a way to kick it off manually.

Company won't fund a spreadsheet add-on.

Any ideas/suggestions?

Accepted answers

Bill Sheboy

Hi @Jeff P

Do you need this one time?

If so, you could create a Scheduled Trigger rule with a JQL expression to select your issues, run it one time, and then disable or delete the rule.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Jeff P

Do you need this one time?

If so, you could create a Scheduled Trigger rule with a JQL expression to select your issues, run it one time, and then disable or delete the rule.

Kind regards,
Bill

Jeff P_1irk0f

I need to run it at will.

Jeff P_1irk0f

Can I trigger a multi-issue automation from any one issue?

Bill Sheboy

In that case, you would need to change the JQL in the trigger when needed and then enable the rule, run it, and then disable it.

Unfortunately, the Manual Trigger for Data Center rules does not support User Inputs yet, and that would be a workaround.

Another way to solve this is: consider when / why you need to run the rule. That is, does something change in the issue data which could be used to trigger the rule? If so, that could be used as the trigger.

Jeff P_1irk0f

I'd love to use a value change to trigger the update but in order to change the values in many issues at the same time we need to use AR (or a different spreadsheet plugin that the company won't pay for). The issue with that is AR doesn't appear to be able to trigger anything upon check in.

I need to run the script against every open issue in the project so I don't think I'd need to update the JQL. If a scheduled trigger can start and run a script against all issues in a project that might work, this assumes a non-admin can enable/disable it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center