Prerequisites
Required Jira Permissions
The Jira account you use to install must have these permissions:| Permission | Description |
|---|---|
| Assign issues | Ability to assign issues to users |
| Close issues | Ability to close issues |
| Create issues | Ability to create new issues |
| Delete issues | Ability to delete issues |
| Edit issues | Ability to edit existing issues |
| Link issues | Ability to link issues to one another |
| Transition issues | Ability to transition issues between statuses |
Learn more about Jira permissions in Atlassian’s documentation.
Required OAuth Scopes
Rootly requests these OAuth scopes during installation:View all 28 OAuth scopes
View all 28 OAuth scopes
Read permissions:
read:application-role:jiraread:avatar:jiraread:field-configuration:jiraread:group:jiraread:issue:jiraread:issue-status:jiraread:issue-meta:jiraread:issue-security-level:jiraread:issue-type:jiraread:issue-type-hierarchy:jiraread:issue.changelog:jiraread:issue.transition:jiraread:issue.vote:jiraread:priority:jiraread:project:jiraread:project-category:jiraread:project-version:jiraread:project.component:jiraread:project.property:jiraread:status:jiraread:user:jiraread:user.property:jira
write:attachment:jirawrite:comment:jirawrite:comment.property:jirawrite:issue:jirawrite:issue.property:jira
Connect Jira to Rootly
The OAuth flow connects your Jira Cloud instance to Rootly. You’ll be redirected to Jira to authorize the connection, then returned to Rootly automatically.Authorize in Jira
You’ll be redirected to Jira. Verify you’re installing on the correct instance, then click Accept.



Your Jira Cloud instance is now connected to Rootly.
Installing Additional Instances
If your organization uses multiple Jira Cloud instances, you can connect them separately.A Jira Cloud instance is not the same as a Jira project. An instance is a separate domain (e.g.,
company.atlassian.net). You can have multiple projects within one instance — most organizations have a single instance with multiple projects.- Go to Integrations and search for Jira Cloud
- Click Set up another instance
- Follow the same authorization flow
Setting Up the Jira Webhook
To enable Jira → Rootly sync, you must configure a webhook in Jira. This allows Rootly to receive events when Jira issues are created or updated. Without this step, changes in Jira won’t reflect back in Rootly.Configure the webhook
Give it a descriptive name (e.g., “Rootly Webhook Listener”) and ensure the status is set to Enabled.

Add the Rootly webhook URL
In Rootly, go to Integrations → Jira → Configure and copy the webhook URL. Paste it into the URL field in Jira.



Filter by project (optional)
To limit which projects send events to Rootly, add a JQL filter under Issue related events. Leave this blank to receive events from all projects.

Select events
Choose the Jira events you want Rootly to receive — at minimum, select issue created and issue updated.

Keep request body enabled
Ensure Exclude body is not checked. Jira may enable this by default, but Rootly requires the full event payload to process events correctly.

Your Jira webhook is now configured for bidirectional sync.
Verify Installation
Once connected, confirm the integration is working end-to-end:- Check integration status — The Jira tile in Rootly should show Connected.
- Test Rootly → Jira — Create a test incident and verify that a Jira issue is created in the expected project.
- Test Jira → Rootly — Create or update a Jira issue, then check the Alerts page in Rootly to confirm the event arrived.
Troubleshooting
Jira integration not appearing after OAuth
Jira integration not appearing after OAuth
Issue: After completing OAuth, Jira doesn’t show under Connected Apps.Solutions:
- Ensure you completed the full OAuth consent flow without navigating away
- Confirm your Jira user has admin or manage apps permissions
- Log out of other Jira accounts and retry authorization
- Revoke the app in Jira (Settings → Apps → Manage Apps) and reconnect
Rootly cannot access Jira projects
Rootly cannot access Jira projects
Issue: Jira connects but no projects appear in Rootly.Solutions:
- Verify your Jira account has Browse Projects permission
- Check project-level permissions for Create Issues, Edit Issues, and Add Comments
- Re-authenticate to refresh your permission scopes
Issue creation fails
Issue creation fails
Issue: Integration connects but Rootly can’t create issues in Jira.Solutions:
- Verify your Jira user has: Create Issues, Edit Issues, Assign Issues, Add Comments
- Check for required custom fields in Jira that aren’t being populated by Rootly
- Confirm the issue type exists in the selected project
- Review Jira workflow validators that may block external issue creation
Webhook events not appearing in Rootly
Webhook events not appearing in Rootly
Issue: Jira events don’t show on Rootly’s Alerts page.Solutions:
- Verify the webhook URL in Jira matches the one from Rootly
- Ensure Exclude body is NOT checked in the Jira webhook settings
- Confirm the webhook status is Enabled
- Check that your JQL filter (if used) includes the project you’re testing with
Uninstall
To remove the Jira integration:- Go to Configuration → Integrations and find Jira
- Click Connected to reveal the disconnect option
- Click Disconnect








