Installation
Premissions Required
You must be an Owner or Admin user in order to install Jira Cloud on your Rootly organization account.
You must also have admin rights to your Jira Cloud instance.
Service Account
To ensure the best long-term stability of your integration, it's recommended that you integrate with a Jira service account, instead of a personal account.
The Jira account you're using to install need to have the following permissions:
- Assign issues: Ability to assign issues to specific users.
- Close issues: Ability to close issues.
- Create issues: Ability to create issues.
- Delete issues: Ability to delete issues.
- Edit issues: Ability to edit issues.
- Link issues: Ability to link issues one issue to another.
- Transition issues: Ability to transition an issue from one status to another.
The Jira account you're using to install need to have the following oauth permissions:
- read:application-role:jira
- read:avatar:jira
- read:field-configuration:jira
- read:group:jira
- read:issue:jira
- read:issue-status:jira
- read:issue-meta:jira
- read:issue-security-level:jira
- read:issue-type:jira
- read:issue-type-hierarchy:jira
- read:issue.changelog:jira
- read:issue.transition:jira
- read:issue.vote:jira
- read:priority:jira
- read:project:jira
- read:project-category:jira
- read:project-version:jira
- read:project.component:jira
- read:project.property:jira
- read:status:jira
- read:user:jira
- read:user.property:jira
- write:attachment:jira
- write:comment:jira
- write:comment.property:jira
- write:issue:jira
- write:issue.property:jira
You can learn more about Jira permissions here.
Locate Jira Cloud on on the Integrations catalogue and select Setup.
You'll be presented with the following installation page. Double check that you're installing the correct instance before you confirm the installation by selecting Accept.
That's it! You're all set to begin automating Jira workflows now.
If your organization leverages mutliple Jira Cloud instances, you can install additional instances using the same procedure above.
A Jira Cloud "instanance" is NOT the same a Jira "project". Think of a Jira Cloud instance as a separate domain. You can have mutliple Jira projects within a single instance. Most organizations should only have a sigle instance, but multiple projects.
To install additional instance, locate Jira Cloud on on the Integrations catalogue, again, and select Set up another instance.
The ensuing steps are the same as installing the first instance.
Ensure that you are logged into the instance you're intending to install on the same browswer window that you have Rootly opened on.
Rootly not only allows you to create tickets into Jira, it is also capable of receiving updates from Jira and updating the incident to reflect the changes from Jira. To do so, you'll need to configure webhooks in Jira.
As a Jira Admin, navigate to Systems > WebHooks in your Jira Cloud instance. Then select + Create a WebHook
Give the webhook an easy to identify Name (e.g. Rootly Webhook Listener) and copy the webhook URL from your Rootly platform.
Ensure the webhook's Status is Enabled.
Copy the webhook URL from the Rootly integrations page into the URL field in Jira.
If you do not want all your Jira projects to send events to Rootly, you can filter for them in the Issue related events JQL query.
Select the specific events you'd like to listen for.
Finally, ensure that you DO NOT check the Exlude body checkbox. Sometimes, Jira webhooks will have this checked by default.
Once all of the above fields are entered, select Create to save the webhook configuration.
Now you'll be able to see Jira events appear in the Alerts page on your Rootly platform. You can test this by creating or update a test ticket in Jira. If the event appears on the Alerts page then you'll know the webhook is working.
You can uninstall your Jira Cloud instance on Rootly by can navigating to Integrations > Jira on and selecting Delete.
If you need help or more information about this integration, please contact [email protected] or start a chat by navigating to Help > Chat with Us.
