You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have received e-mail regarding change of automation from single project to global automations only with limitations per month.
We are currently on JIRA Free and since we have a lot of automations I am trying to find out if this change of how many automations per month on global automation will be valid as well for FREE version too?
Since we have quite complicated Workflow scheme - we would need to rebuilt it all, otherwise we would run out of automation in first week.
Is there any way how to find out how many automations are executed every day/week/month?
As I have red in the email it should be 1000 for Work Management, 5000 for Service Management and some number for Confluence.
Please do you know if this will be the case as well on free version?
Hello @Jan Šimek
Under the current system the report mentioned by @Paul Heath Armengol shows only the usage of Global Automation rules.
As noted in this article there will be a new usage report available on October 1 to help you understand your current usage and how it counts towards the new packaging model.
I'm not sure about the email you received, but your single-project rules are not being changed to global/multi-project rules. Instead which rule executions are counted towards the limits is being changed.
Rules (multi-project/global and single-project)will be counted towards the execution limits if the rule successfully executes an action.
If you are on the Free subscription, your rule execution limits will be
100 rule executions against Jira Software projects, in total, per month
100 rule executions against Jira Work Management projects, in total, per month
500 rule executions against Jira Service Management projects, in total, per month
There is a table showing the new limits in the referenced Article.
Make a note in the FAQ section they explain how multi-project rules will be counted.
Let us know if you have additional questions.
I just been warned about this automation. I am a bit confused if the new limit of 1000 usage of rules for the whole Jira work management projects or 1000 per a single project?
Most of the rules we run are on Jira work management projects are over 1000 per project, so if thats the case we cannot use automation for JWM? From the plan, it seems no Premium or entrerise plan will cover unlimited JWM.
I wonder if anyone has similar issues?
The JWM Standard Plan 1000 Executions limit is the limit against the total of executions in all JWM projects in the JWM product.
The JWM Premium plan limit will be 100 executions * the number of licensed users. So if you had 100 licensed JWM users and the Premium plan then your limit would be 10,000 executions total from all JWM projects.
Note also that simply triggering the rule does not count as an execution. The rule has to execute at least one Action, which is also described in the article.
You should also review the new Usage report that should be available to you from the Global Automations page to get an idea of how your current usage would be counted under the new model.
We got 18 people, they alle use confluence, thats workinf fine.
In the automation usage screen it says we could
* use 1700 automation rules for Jira Software, zero are used - which appears correct to me.
* use 200 automation rules for Jira Work Management, all 200 are used - thats the h.u.g.e. problem now.
How can I increase the number of licensed users?
With regard to automation usage limits the number of licensed users matters only if you have a Premium subscription. Do you have a Premium subscription?
If you have a Standard subscription the limits are locked and not changed based on the number of licensed users.
Thanks Trudy for your prompt response
We do have a Premium Subscription.
Meanwhile I recognized my mistake. In the admin area for the product I have assigned a newly created group "all employees" to the product JWM - that did increase the count of automations we can executed. It did take a night to update the usage screen.
My mistake was to assume it is sufficient to provide users access to the product. Which wasnt.