Atlassian OAuth Integration

Atlassian is used for sign-in and for the shared connection behind JSM and JSM Operations.

Prerequisites

• You can sign in to RectifAI with Atlassian.
• The connected Atlassian account can access the target Jira site.
• The account can read projects and create issues in the selected project.
• The selected Jira workflow contains the statuses and transitions you expect RectifAI to use.
• If using JSM Operations, the account can access the relevant ops teams.

Add the Atlassian integration

1. Sign in to RectifAI with Continue with Atlassian if you have not already created your account.
2. Open your workspace.
3. Go to Workspace -> Integrations -> JSM if you want Jira Service Management as your system of record.
4. Click Connect Jira.
5. Complete the Atlassian consent flow and approve access.
6. Return to RectifAI and confirm the integration shows as connected.
7. In the JSM page, choose the default Jira project.
8. Choose the issue type for incidents.
9. Optionally configure problem record and action item issue types.
10. Review and confirm the Jira status mappings.
11. If you also use JSM Operations, open Workspace -> Integrations -> Paging -> JSM Operations and confirm the shared Atlassian connection is available there.

Use Atlassian in RectifAI

• Sign in to RectifAI with your Atlassian account.
• Create and sync incident records to Jira Service Management.
• Map RectifAI incident statuses to Jira workflow statuses.
• Create problem records and action items in Jira.
• Use JSM Operations teams for Atlassian-native paging workflows.

Remove the Atlassian integration

1. Open Workspace -> Integrations -> JSM or Workspace -> Integrations -> Paging -> JSM Operations.
2. Click Disconnect.
3. Confirm that the connection is no longer shown as connected.

What happens after removal

• RectifAI can no longer create or update Jira-backed incidents for that workspace.
• JSM Operations paging flows will stop.
• Atlassian-based project, issue type, and status mapping configuration may remain visible in RectifAI until replaced or reconfigured, but it will not be usable without reconnecting.
• Existing Jira issues remain in Jira and are not deleted by RectifAI.

Data handling

• RectifAI removes the stored Atlassian OAuth tokens for the workspace.
• Historical incident records already stored in RectifAI remain until deletion under our retention policy.
• Any Jira issues or Atlassian-side data already created stay in Atlassian unless you remove them there.

Troubleshooting

If you run into trouble during setup or removal, see the Troubleshooting guide.