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

Automations execution limit

Marcin Szymkowiak_d14xnc

Are there any limits to Automations' executions on JSD? I'm asking about old Automations feature not the new one (Automations for Jira that's currently included as built-in function instead of an app).

Especially for automations that works between the projects (like syncing status of JSD issue with issue on Jira Software). Adding that because that's what makes a difference for Automations for Jira executions limit.

There are some strict executions limits for built-in Automations for Jira and now it's confusing - are both using the same execution limits?

Accepted answers

Angélica Luz

Hello Marcin,

Thank you for reaching out Atlassian Community!

For the built-in Automation in Service Desk, there are no limitations at the moment. The idea is that, in the future, this Automation will be removed from Service Desk projects and only the new Automation (old Automation for Jira) will be available.

Just for you to better understand this new automation and the limitations:

If a new automation rule is created and run for a specific project, the executions will be unlimited. This is true for Cloud Free, Standard, and Premium.

If a rule is created and applied to more than one project, it's considered global, so it will be limited. The limits for that are (for a month) 100 executions for Free plan, 500 executions for Standard and 1000 executions per licensed Premium user.

In your case, where the automation works between two projects, it will be considered global and have limitations according to your Cloud Plan.

If you have any other questions about this matter, please let us know.

Regards,
Angélica

All comments

Angélica Luz

Hello Marcin,

Thank you for reaching out Atlassian Community!

Just for you to better understand this new automation and the limitations:

If a new automation rule is created and run for a specific project, the executions will be unlimited. This is true for Cloud Free, Standard, and Premium.

In your case, where the automation works between two projects, it will be considered global and have limitations according to your Cloud Plan.

If you have any other questions about this matter, please let us know.

Regards,
Angélica

Marcin Szymkowiak_d14xnc

@Angélica Luz

Thank you Angélica for your answer.

I know that you will not be able to give me a date but is that removal of old JSD Automations something that may happen in a month / half a year / a year from now? Would be nice to be prepared for that.

Also I hope that one improvement to new Automation (old Automation for Jira) will be made before you decide to remove old Automations in JSD - ability to choose actor in the Cloud versions of Jira. It will be crucial for automations running on JSD issues.

I've seen that this suggestion was made somewhere already if there is an issue gathering interest currently I'd really like to give it my vote also.

Angélica Luz

Hi Marcin,

The migration will be in the coming months, we are not sure when, but I don't think it will take a year.

All the rules will be migrated, it's not necessary any action from your side, you don't need to worry about that.

Regarding the feature, we also don't know what improvements will be added.

I found a feature similar to the one you mentioned:

Allow user who triggered event to be rule Actor (or issue reporter, etc)

If that's not the one, please give us more details so I can search here.

Marcin Szymkowiak_d14xnc

@Angélica Luz

I've found issues that are more close to what I meant myself:

https://codebarrel.atlassian.net/browse/AUT-56

or at least:

https://codebarrel.atlassian.net/browse/AUT-1220

Guaraci Nakamura

Hi guys. We have these automations below which have been consuming the "Executions" limit, and would like to know if you have some recommendation to consume less.

Captura de tela 2022-05-17 105139.png

1 - When a Story issue is created, a standard text is included in the "Description" field. The problem is consuming "Executions" for all created issues, including subtasks. PS: Initially I was wondering to create a new custom field with a standard text (e.g. "Description xx"). However, I gave up this option because the project has some years and already has thousands of issues, so replace the current Description field to the new one would mass this fields once contains not only text but pictures, tables.

Captura de tela 2022-05-17 104748.png

2 - Attribute to the "Start Date" field the date when one of 5 types of issues are transitioned to "in progress" or "dev doing" status. The problem is consuming "Executions" for all created issues, including subtasks.

Captura de tela 2022-05-17 104200.png

Marcin Szymkowiak_d14xnc

Change the automation from Global to Single Project but you will need to create a copy for each project you have on Jira (and want to have this automation running in it).

Guaraci Nakamura

@Marcin Szymkowiak This rule is really applied to both projects we have (two). What would be the benefit in doing 2 different automation?

Marcin Szymkowiak_d14xnc

@Guaraci Nakamura

Single Project automations doesn't count towards automation executions limits. Only multi-project and global do.

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-desk