Integrations

Jira Service Management

Automatically open Jira issues whenever an Uptime monitor fires an incident. The integration connects your Atlassian Cloud site to xUptimeMonitor so that on-call engineers can triage the outage from the tools they already use.

← Docs home Configure in dashboard

Prerequisites

  • An Uptime plan that includes the Jira integration.
  • Administrator access to the target Jira Cloud site (for example https://acme.atlassian.net).
  • A Jira user with permission to create issues in the chosen project.
  • An Atlassian API token created for that user (tokens are generated at id.atlassian.com/manage/api-tokens).

Connect your Jira site

  1. In the dashboard go to Dash → Account → Integrations and locate Jira Service Management.
  2. Check Enabled to activate the configuration form.
  3. Enter the Jira Cloud site URL (for example https://acme.atlassian.net).
  4. Provide the Atlassian account email that owns the API token.
  5. Fill in the target Project key (the short code visible in your Jira board) and Issue type (for example Incident or Task).
  6. Paste the API token. Tokens are stored encrypted and are write-only; you can paste a new token later to rotate credentials.
  7. Select Save changes. A confirmation message appears when the connection succeeds.

If the integration is not available on your plan, the form is read-only. Upgrade first, then refresh the page to unlock the controls.

What gets synced

  • Each open incident in statuses investigating, identified, monitoring, or in_progress is queued for Jira.
  • The worker creates a new issue containing the incident title, timeline, affected monitor, and status page links.
  • When an incident recovers we add a comment to the linked Jira issue and update the state field tracked in Jira.
  • Retry logic handles temporary API failures up to five times before marking the sync as errored (visible in the incident sidebar).

The worker runs continuously; newly opened incidents appear in Jira within a few minutes once DNS/custom-domain limits allow the request queue to proceed.

Troubleshooting

  • Check the incident’s Jira panel in the dashboard. Errors such as “401 Unauthorized” or “Project not found” surface there.
  • Verify the API token is active (tokens can be revoked from the Atlassian profile page). Paste a fresh token to rotate credentials.
  • Ensure the Jira user has Create Issue permission for the specified project and issue type.
  • Disable the integration toggle to pause syncing without losing your stored settings. Re-enable once credentials are corrected.

Removing the integration

To disconnect Jira, uncheck Enabled and click Save changes. Optionally paste a blank value in the API token field to wipe the stored secret. Existing Jira issues remain in Atlassian and are no longer updated by xUptimeMonitor.