Automation for Jira vs Service Desk automation

We get asked quite often why we offer Automation for Jira when Jira Service Desk comes with automation as a bundled feature. Jira Service Desk's built-in automation is great, but Automation for Jira takes it to a new level in terms of power and ease of use. We believe Automation for Jira offers significant advantages over Jira Service Desk's in-built automation that help ALL teams automate their processes and enable you to capture even more business requirements.

Highlights

Smart values - Smart values allow you to substitute in any value from any object
that the rule has access to. E.g. The status of the parent issue, the email address of the person that edited the issue, or the before and after values of an issue edit. These are allowed in most fields enabling you to do things like:

This is only a small taste of what you can do with smart values.

More components - With over 50 components to choose from you capture many more processes than with the 32 components shipped with Service Desk.

Jira Software support - You can listen for changes to sprints, versions and also update software fields on issues. Enabling you to automate a lot of your release processes.

Working with related issues - You can also branch out and act on any related issue. E.g. For all sub-tasks, set their priority to the same as the parent issue, comment on all linked issues, transition the Epic of this story, and many more use cases

User Interface

We take great pride in the UI and believe it be one of the slickest on the market. Here is a comparison of Automation for Jira vs Service Desk for a simple rule to edit the priority and add a comment:

Automation for Jira
Automation for Jira

Service Desk
Service Desk

Detailed Feature Comparison

Automation for Jira Jira Service Desk Automation
Cloud & Server
Active development 320 issues closed in 2018 30 issues closed in 2018
Project types supported All Service Desk projects
Jira Software support
Project Admins can create rules
Permissions for who can create rules
Service limits to protect Jira
Global Rules
Multi-Project Rules
Customisable Rule Actor ✅ Per rule in Server ✅ Per project
Run rule as user who triggered event
Triggers 22 12
Conditions 6 11
Actions 26 9
Execute rules on related issues
Scheduled Rules
Copy values between issues and fields
Math functions / calculated fields
Comprehensive smart value substitutions ❌ 9 variables in emails
Auto approve
Audit logs ✅ Rule/Project/Global ✅ Rule
Integrations out of the box Stride, Slack, HipChat, Twilio, Webhooks Webhooks
Integrations in marketplace ✅ In Server
Write your own integrations ✅ In Server