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

Global automation

Ori Bergman

Hey

i have 4 project on my Jira.
and i want to add rules that apply to all four of them.
For example, i want to add a transition rule that from status "To DO" to the rest, the issue moves boards, from backlog to Board. For each specific Project.
But every time i try and make this Automation, Jira forces me to choose a project. Therefore, i am obligated to copy the rule for every project.

Accepted answers

All comments

Manoj Kumar Gangwar

Hi @Ori Bergman Welcome to the community!

Global automation rules can only be configured by Jira admins. Do you have admin privileges for your instance?

Sarp Egemen

Hi @Ori Bergman ,

Make sure you add automations through the "Global Automations" tab rather than through "Project Settings > Automations."

Follow these steps:

Open Jira System Settings.png Global Automation Tab.png

(PS: While in the Global Automations tab, you can also modify the scope of your existing rules to make them global.)

Let me know if you need any additional help!

Sarp Egemen

Hi @Manoj Kumar Gangwar ,

I’m sure you’re aware, but just to confirm, the user mentioned their permission level as Product Admin.

All the best!

Bill Sheboy

Hi @Ori Bergman -- Welcome to the Atlassian Community!

Adding to the other suggestions provided...

What are the types of your projects: company-managed or team-managed?

This is relevant as you want to transition issues in different projects:

For company-managed projects, the status values are all shared globally...even when the specific workflows could be different. And so a rule which transitions issues in different projects is less likely to have problems with the Transition Issue action.
But for team-managed, each project's configuration is different with unique status values...even when they have the same Status Names and workflow patterns. As a result, a rule will likely run into problems using the Transition Issue action, and may need instead to use the REST API endpoint to update the issues.

Kind regards,
Bill

Ori Bergman

Hey

Thanks for the quick Replay
i see that our projects are team Managed.
But i do have some Automations that are relevant from all the projects.
like i wrote above, the automation rule moving issues from Backlog to the main board once status is changed.

As you see. it doesn't allow me to apply this rule for all projects and to add now the same rules for each project seems inefficient.

Thx
Ori

Bill Sheboy

Thanks for that information, and...

Please note the Move Issue to Board action was specifically added to automation because of another design problem / choice for team-managed projects:

Unlike a company-managed project, for a team-managed project the status value is independent of when an issue is shown on the board versus the backlog. That is, the status mapping to board columns does not impact display on the board!

Thus a global or multiple-project scope rule using this action would need to use an if / else block, testing for each project to also select the board. For example:

if / else condition
- condition: project equals ABC
- action: move issue to board for "ABC board"
else / if
- condition: project equals DEF
- action: move issue to board for "DEF board"
...

Ori Bergman

hey guys

yes
i am an

organization admin

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud