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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are on Sever now and Planning to move to Cloud.
Observed that "Automation for Jira" is not available for Cloud, Will it comes as Inbuilt with Cloud ?
Any help would be appreciated.
Hi @Linda Milne_Togetha Group_ Thanks for the information.
What does 500 executions per user means?
I am the admin of my site and All the automation rules will run with my Name.
Suppose if we have scheduled rule executes for every 2 hours in a day which means the single rule will executes 360 times in a month with my name.
So will I be left with 140 executions ? for the month ??
If we have 2 scheduled rules, that is it ? All other rules will not work for Standard Plan !!
This is how the Jira cloud Automation works ? Please clarify!
Thanks in Advance
Customers on Free and Standard plans have access to a limited monthly trial allotment of global and multi project rule executions (100 and 500 per month, respectively).
Rule execution (from the docs) is:
Your usage is measured by the number of rules that have been executed during your billing period.
Any time an event fires as a result of an automation rule you have enabled, it will count as a rule execution.
For example, if you have created a rule that fires whenever an issue transitions to Done, this will count as a rule execution. Even if the rule does not perform an action, as long as it has been triggered, it is considered an execution.
A bonus is that:
Single-project rule executions do not count towards your usage. A single-project rule is a rule that automates a task or process that only affects one project.
So, can you reduce the number of times you execute the global / multi-project rules and / or move to running some rules from within the projects?
Hi @Linda Milne_Togetha Group_
Thanks for the Clarification.
Ok, Limitation is only for Global / Multi-Project rules.
Then we can use the same rules in Project rules right ? And there is no limitation for Project rules. In Project rules we can run schedule jobs and execute number of times without any limitations.
Please correct me if I was wrong!
Only burden is to write the same rules for every project, That is not a big deal...Some thing is better than nothing.
Once again thanks a lot for taking your time and writing all this.
The key here "Single-project rule executions do not count towards your usage. A single-project rule is a rule that automates a task or process that only affects one project."
Madhu, if your daily automation is cross-project (includes more than 1 project) you can try to workaround it by splitting your rule among the projects. In case it's a global automation rule (available again for multiple projects) you can simply copy your rule in every single project.
Of course, you can switch to the Premium plan where rule execution limit is a lot scalable. That plan limitations are based not only on per product used, but also per licensed users. "Premium users have 1000 global and multi-project rule executions per paid user per month. Ex: 200 users in Jira Cloud Premium will have 200,000 monthly global/multi-project rule executions per month."
Hope that helps!
Thanks for taking your time and clarifying..
We will try to split the rules among the projects. Anyway we will have 500 global rule executions to work with if we have cross project requirements.
Looks like this 500 executions for the whole year ? Or it is a monthly executions limit for cloud standard ?
When you switch to Jira Cloud you'll have a good overview over the usage of the automations addon, including the number of executions you have used, how many days you have left until the counter is reset and on which date it will be reset exactly.
And yeah, it's reset on monthly basis, not on yearly.
@Linda Milne_Togetha Group_ speaks sooth. Moreover, with a bit of twiddling, you can export automations out of server and import them to Cloud. HOWEVER, you need to make a stop in the middle.
Export from Server. Look at all the object IDs in the exported JSON file and then replace them with what the object ID is on your target cloud instance. Import them. They work.
You can import them without error withOUT making that stop but a) they won't work and b) it's not as easy as just selecting the missing bit because the object ID changed; the whole chunk of the rule is missing and needs to be redone.
Hi @Madhu Reddy
Automation for Jira certainly is part of cloud. If you can get to the "project settings" of a project, you can access the "Automation" section for that project.
It's worth noting, if you are on Jira standard, multi -project and global automation rules have monthly execution limits. See @Linda Milne_Togetha Group_ link for details.