Automation basics
Understand the general concepts and best practices of automation in Atlassian cloud products.
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
To manage project and team automations, you must have the appropriate permissions:
Company-managed projects: You’ll need the Administer projects and Browse projects permissions for your project. Learn more about permissions for company-managed projects
Team-managed projects: You’ll need Administrator access for your project. Learn more about permissions for team-managed projects
Team automation: You’ll need Admin role in operations to access team automation. Learn more about member roles in operations
To manage global automations, you’ll need the Administer Jira permission. Learn more about global permissions in Jira Cloud.
This action is only available on Jira Service Management Premium and Enterprise plans.
Go to Automation and select Create rule.
Select the Run script using Jira Edge Connector action for your rule.
Select Connect to create a connection with Jira Edge Connector. Connections allow your automation rules to make changes in other tools and products.
Enter a unique name for your API key and select Create API key.
Copy the API key you created and add it in the apiKey field in your Jira Edge Connector configuration file. Read more about configuring JEC.
Enter name of the action mapped to the on-prem script you want to run. This is found in the actionMappings → mappedAction field of your JEC configuration file.
Add key-value pairs you want to include in the JSON message sent to the on-prem system. Jira doesn't validate your key-value pairs, so make sure you verify them.
Save your rule.
You can use the same API key across multiple rules. However, removing your API key will cause all automation rules using the API key to stop working.
Was this helpful?