Automation packaging model for Jira Work Management

[Saranya]

Hi,

We have a team of 140 users who rely on JIRA work management. Our workflow heavily relies on automation rules, and we run around 300,000 automations every month. However, we are currently encountering difficulties due to the changes in the Automation packaging model. Could you kindly suggest an alternative solution for us?

Thank you

[Valerie Knapp]

Hi @Saranya , thanks for your question.

It depends a lot on what you are using the Automations for.

In some cases, it might be possible to use other configurations to achieve the same outcomes.

For example, if you have an automation that is populating a field or creating Subtasks from the trigger of a transition, some of these things you could also do with workflow conditions / validators or post functions - How to create workflows for company-managed projects? | Jira Work Management Cloud | Atlassian Support

You could also consider to change some of the configuration of things like the screens, using the field configuration scheme to make some fields mandatory for the creation of an issue, and in that way, you can avoid to have to use an automation to populate them later.

If you are still stuck, you could reach out to an Atlassian partner to get some more in-depth analysis for how you can manage this, but this will be at a cost - Atlassian Partner Directory

I hope this helps.

Cheers

[Sebastian Krzewiński]

Hi @Saranya 

Did you try to review your rules and optimise it like Atlassian advise here - https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099 ?

Regards,

Seba