Service Desk automation is very focused on the Service Desk/Helpdesk use case, whereas Automation for JIRA was designed to be a more generic solution for a broader set of problems. As such, Automation for JIRA can be applied to JIRA Core, JIRA Software and JIRA Serice Desk.
In terms of capabilities, as of version 1, Automation for JIRA ships with roughly 24 triggers, conditions and actions (including 3rd party integrations with Slack and Twilio) compared with the 12 Service Desk ships with.
You can copy/clone a rule by using the "create" action and passing in values from the original issue using smart values. If you can wait a week, I'm working on a specific clone issue action. I'm in travelling until monday so it will have to wait to then.
You can all the actions in product when you select to add an action, but it may be worthwhile for us to create a confluence page with a comprehensive list.
Automation for JIRA is far more powerful than the SD one. As SD Automation uses a gui, it is far more limited in flexibility. The vast majority of my service desk automation is done using Automation for JIRA.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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