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?
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.
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.
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:
If that's not the one, please give us more details so I can search here.
Thank you for reaching out to Community!
The limitation of 1000 executions is for each premium licensed user. So, for example, if your site has 200 premium users, the limit will be 200,000 global rule executions.
For more information about the limits, please, check the FAQ below:
Many thanks for your fast response @Angélica Luz
do you mean user = agents (at least for Jira Service Desk (JSD)) ?
lets say we have 50 Agents for JSD - if we upgrade them to Premium we could run 50k Automations
Analog for Jira Software lets save we have 100 users - if we switch them to Premium we would have 200k global executions ?
did I understand you and the FAQ correctly ?
got the answer from Atlassian support: just in case somebody wants to know as well:
The Global Execution limit for the Premium Plan is 1000 per licensed user per month.
This includes Jira Software Premium (users) and Jira Service Desk Premium (agents).
If you have 100 users for Jira Software Premium and you have 50 agents for Jira Service Desk Premium that would give you a total of 150,000 global executions per month.
Two more questions regarding the limits:
The limits from JSD and Jira Software subscriptions are summed up and can be used for any automation? (so if there is no automation running on JSD projects the quota can be used for automation running on multiple projects in Jira Software?)
I've found out in your documentation an entry like this:
What executions count towards my usage?
One exception to this is the cross-product Issue create action. For example, if you want to create an issue in Jira Software based off an event in Jira Service Desk – this will count as a single-project rule, not a global rule.
That's limited to only Issue Create action and issue clone action will be counted, right? And I can't make any other actions in the same automation?
As far as I know and understood the documentation the JSD automation have still no limitation
The limitation does only count towards Jira Automations (codebarrel) and then only to automations on multiple projects. So there is also no limitation if you use the Jira Automation only for one project (check the Automation settings - there are no execution limits if you set "Single Project"
This automation is also only limited if you select multiple projects. There are no limits if you select "Single project"
About the Sum: I guess as the limitation counts only towards multi-project automations and is related to the paid accounts the multi-project automations from JSD and Classic Software projects will be calculated together towards your execution limit if those are multi-project automations.
Testing on my local site, the Clone action didn't count as global execution. I believe that it's also considered as a "Create issue".
I created a simple rule to clone the issue to a Software project when an issue on Service Desk is created. The rule was created on the SD project.
I created 5 issues on the SD project and it was cloned correctly. None of them was counted on the execution limits.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events