New Automation Limits - Tripled our License

[RSavage_stellarindustrial_com]

We have created a lot of automation rules for our service desk to help manage queues and priorities.  This helps our team manage who services our customers.

As of November, Atlassian changed the license model.  We are not looking at OVER TRIPLE the cost for our automation than we had before.

We currently have the standard license and will need to go to premium.  We don't want or need all the premium services.

What options do we have besides finding a new service desk software?

[Joseph Chung Yin]

@RSavage_stellarindustrial_com -

My recommendation that you want do is to review all of your existing automation rules to avoid unnecessary executions by conduct the necessary modifications as needed.

Here are some recommendation as stated by Atlassian -

• Configure your rules to run where they need to: Make sure your rule runs only in the Jira projects (or Confluence spaces) you want it to run in.
• Add conditions to your Automation rules: Ensure that actions occur exactly when you want them to in order to maximize the value you get out of your rules.
• Disable rules: Monitor your rules and identify the ones that are either running too often or that you don’t need, and disable them to prevent wasteful rule runs.

Take a look on how rule execution is calculated - https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Trudy Claspill]

You might also consider if some of the same functionality can be handled through workflow automation (i.e. Post Functions) and leveraging third party apps.

As part of your rule review you might also consider if some rules that are running on demand could be changed to run on a schedule and handle the update of multiple issues in one execution.

[Joseph Chung Yin]

Good suggestions my leader member...

Best, Joseph

[Eric B_]

@RSavage_stellarindustrial_com 
We had a similar story where when they changed the automation limit our Jira instance stopped working after a few days because most of it was running off automation set for each environment, in a panic we needed to change to Premium immediately.

This almost caused us to get rid of Atlassian all together due to the High cost of Premium verses Standard. After debate we were able to find a solution that worked, which is using the API and some Coding to be able to move all our automation off of Jira and host it locally.