Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

I'm very confused about the different Automation options I'm seeing..??


TL;DR - What's the difference between Service Desk Project -> Project Settings -> Project Automation and Service Desk Project -> Project Settings -> Automation?

I'm trying to pick up the pieces of what was left after the person I had setting up my Jira is no longer available.  

I know at one point we were using a plugin for Automation rules, and I still see this under "Manage Apps", but it looks like it's not active at all because it's telling me I need to sign up for a trial:


When I go to System -> Automation, I see this, which looks just like the screenshots in the plugin shown above:



However, most of these rules are disabled, some of the ones that are enabled are showing errors, and the notice at the top is showing that we've already maxed out our execution limit after only 3 days, so none of the rules are going to be running anyway.

So now here's where my confusion starts to kick in.  If I go to my Service Desk project, and then go to Project Settings, I see two separate options for Automation in there.

One just says "Automation" and the other says "Project Automation".


The one that says "Project Automation" is the same as what's shown above, and is simply the project level rules that built into that general Automation.

However, the one that says "Automation" here is completely different, and looks like this:

image.pngThese are the rules that seem to be driving the bulk of our Automation with my Service Desk.  I make adjustments here and they take affect accordingly.  Also, they always run.  I'm not getting any notices about maxing out our execution limit or anything like that.

I have no idea what the difference is between these Automation sections, though, and I'm very confused.

Anybody have some guidance for me on this?  I don't understand why I need the paid executions Automation if I can just use this other one that's free, but I also don't understand where it's coming from or why it's separate, and what disadvantages I might have to using it the way I have been..??

Any information on this would be greatly appreciated.  Thanks!


1 comment

Hey @Drew Angell ,

John from the automation team here. It is a bit confusing I must confess. Automation for Jira was recently acquired and built natively into Jira Cloud. We are working on aligning the two automation engines so Jira automation (i.e your screenshot below) is the one true automation engine and everything will live in one place.

We ran a few webinars and these questions came up a lot. We documented them here:

Hope that helps!





Log in or Sign up to comment
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,251 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you