Frontline global cloud migration company, Atlassian, has introduced a new packaging for its Jira Cloud Automation.
The company is seeking to expand the same packaging model that was released with Confluence Automation earlier this year to its Jira Cloud family of products with the changes to come into effect on November 1.
Head of Product Management, Confluence, Genevieve Sheehan, who announced the launch of Atlassian Automation in January, stated that it worked for Jira, the Confluence Cloud Premium and the Enterprise family.
Automation for Confluence is powered by the Atlassian platform and operates off of triggers, conditions, and actions built into rules. With Automation, companies and businesses get to build their own automated systems to deal with sets of important processes with a trigger. This helps teams focus on other duties knowing that other day to day routine tasks have been automated.
But then the big question would be – what’s changing?
According to an Atlassian Community blog-post, the new packaging model brings a simpler, more consistent way to measure automation usage.
Automation usage is measured differently across both rule types and Atlassian products. Currently, there is only one limit for all Jira Cloud products. Every time an Automation rule runs, it counts towards that limit regardless of whether it performed a successful action or not.
The post also gives us a summary of the key changes for Jira Cloud products:
1. Only rules that perform a successful action will count towards the limit
In today’s model, rule runs count toward your usage limit, even if they perform no actions.
For example, let’s say you have the following rule set up:
Trigger: When an issue is created
Condition: If issue type = Bug
Action: Set Affects version field to Last released version
This rule would trigger and count toward your execution limit every time an issue was created, even for issues that aren’t bugs. In the new model, the rule will only count if the issue created is a Bug and the Affects version field is successfully updated.
2. Each Jira product will have its own limit:
In today’s model, customers get a single, pooled limit across all Jira products in today’s model. For example, if a customer has JSW Standard and JSM Free, they would get a total of 600 automation rule runs per month (100 from JSW Free and 500 from JSM Standard) that can be used across both products.
Each Jira product will have its own usage limit in the new model. Every automation rule draws on the limit of a specific Jira product when it runs. We have even increased the limits for our Free and Standard plans. Automation limits in the new model are shown below:
Read more at:
https://lnkd.in/depmbPQD
Philips Babatunde