Jira

Turn Monita issues into Jira tickets — automatically for anything at or above a severity you choose, or manually with one click from an issue. The link is two-way: closing the ticket in Jira resolves the issue in Monita, and resolving in Monita comments on the ticket.

Connect Jira

You need to be a Monita admin, and your Atlassian account needs access to the Jira site and projects you want tickets in.

1. In Integrations, find the Jira card and click Connect Jira.

2. Atlassian shows its consent screen. Approve the requested access (reading and writing Jira issues, and managing webhooks — the webhooks power status sync).

3. Back in Monita, finish the configuration on the Jira card:

   • Jira site — only shown if your Atlassian account has more than one site.
   • Default project — where tickets are filed unless a mapping says otherwise.
   • Issue type — the Jira issue type name to create (Task by default).
   • Minimum severity — the auto-file floor (high by default): issues at or above it file automatically.
   • Auto-create — turn automatic filing off entirely if you only want manual filing.

4. Click Save. The integration goes active once a site and default project are set.

What gets filed

When a Monita issue opens at or above your severity floor (or you file one manually), Monita creates a Jira issue with:

• Summary: [SEVERITY] issue title — for example [HIGH] Meta Pixel purchase volume drop.
• Labels: monita plus the severity, so you can filter and report on them in Jira.
• Description: what fired, with a View in Monita link back to the issue.

The Monita issue shows a Jira badge with the ticket key, linking straight to the ticket.

Manual filing

Any issue can become a ticket regardless of the severity floor: open the issue in Issues and click Create Jira issue. It uses the same project resolution as auto-filing. An issue links to at most one ticket.

Project mapping

By default everything files into the default project. If different Monita projects belong to different teams, map each Monita project to its own Jira project on the Jira card — the mapping overrides the default per project.

Two-way status sync

Once connected, status flows both ways with no setup on the Jira side — Monita registers the necessary webhooks itself:

• Jira → Monita: moving a linked ticket to any Done-category status resolves the Monita issue. Moving it back out of Done reopens the issue. Each sync is recorded on the issue timeline.
• Monita → Jira: resolving a linked issue in Monita (by hand or by auto-recovery) adds a comment on the ticket, so the assignee sees the all-clear where they work.
• Issues you have muted or acknowledged in Monita are left alone — a human took over, and Jira transitions won’t flip them.
• Deleting the ticket in Jira removes the link and notes it on the issue timeline; the Monita issue itself is untouched.

Reconnecting

One Jira connection serves the whole organisation; connecting again replaces it. If the card shows an error state, Atlassian has invalidated the stored token (this happens after long inactivity) — click Reconnect and approve again. Connections made before status sync existed also need a one-time reconnect to grant the webhook permission.