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

Automation Rules for Service Management Projects

Stanislav Kotakov

Hello everyone ,

I'm trying to figure it out which automation are better .

First case : To create global rules and to apply them to multiple projects .

Second case : To copy multiple automation rules to a single project .

I know that it is kinda situational , but anyways i would love to hear your opinions .

: )

Comments

Marco_6wqmdi

I'd say it depends on the number of affected projects and if there MAY be a reason why the automation needs to be changed for just one of the project. Single Project rules though do not count towards the usage limit (if there are many rule executions) https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Stanislav Kotakov

Good point . Let's take for example the Premium plan which is limited each month to a pooled sum that’s equivalent to 1,000 multi-project or global project rule executions for every user + up to 35,000 users. How are you going to proceed in such case?

Marco_6wqmdi

in this case i'd try to calculate the expected rule executions and depending on this i'd choose if i create a global rule

but on the other hand the more projects you have that would benefit from the automation the less pro arguments can be made for create the same rule for each project.

But I also have to say that our Jira Instance is not nearly that big that i'd ever get in this situation

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