Page your on-call team when a Jira issue is created. A Jira Automation flow sends the issue to JAMS Incident Management, and JAMS calls, texts or pushes your recipients until someone acknowledges. When the issue moves to Done in Jira, the alerts stop.
Plan availability: The Jira integration is included on the Professional plan and up. See Plans & Billing.
What this version does — and doesn't. JAMS receives issues from Jira. Acknowledging an alert stops the escalation in JAMS, but it does not change the Jira issue, and no Jira credentials are needed. Writing back to Jira is planned for a later release.
"Flows" vs. "rules". Jira's newer Automation editor calls automations flows; older sites call them rules. They're the same thing. Below, "Jira flow" always means a Jira Automation flow — not a JAMS flow.
What you'll need
- A Jira Cloud site, and permission to create Automation in the space (space/project admin is enough).
- Admin access in JAMS.
Step 1 — Create a Jira connection in JAMS
- Open Integrations → Jira (under Ticketing & Incidents in the sidebar).
- Enter a Connection name — naming it after the Jira space (e.g.
OPS) keeps things tidy. - Choose who gets notified (people, groups, on-call schedules or Teams/Slack channels) and the channels to use.
- Set the escalation interval — how long to wait for each person before moving to the next.
- Click Save Connection.
JAMS then shows your webhook URL and two ready-made request bodies to copy. You can find them again any time under Show the Jira Automation setup on the connection.
Step 2 — Open Automation in Jira
Open your space and click the ⚡ lightning-bolt icon at the top right. You can also go to Space settings → Automation (on older sites, Project settings → Automation).
Step 3 — Flow 1: alert when an issue is created
- Create a new flow (skip the tour if one appears).
- Add a trigger: Work item created (Issue created on older sites).
- Add an action: Send web request:
- Web request URL: your JAMS webhook URL
- HTTP method:
POST - Web request body: Custom data — paste the Flow 1 body from JAMS
- Headers:
Content-Type=application/json
- Click Turn on flow and name it, e.g.
JAMS – page on new issue.
Step 4 — Flow 2: stop alerting when the issue is done (recommended)
Without this, someone further down the escalation can be woken for an issue that's already fixed.
- Create another flow. Trigger: Work item transitioned, leave From status blank, set To status to your Done status. Add any other end states too (e.g. Closed, Won't Do).
- Action: the same Send web request, same URL — paste the Flow 2 body from JAMS.
- Click Turn on flow and name it, e.g.
JAMS – stop on Done.
Tip — who can edit: when you turn a flow on, Jira asks who can edit it. Prefer a shared option (e.g. space admins) over Private. A private flow can only be fixed by the person who created it — if they're away, nobody else can repair it.
Step 5 — Test it
Create a test issue. Within a minute your recipients are alerted, and the issue appears on the Incidents page. Create another, don't answer, and move it to Done — the remaining alerts are cancelled.
If you've paused alerting (the pause bar on Flows), the test issue is recorded but won't page anyone. Resume first.
Choose which issues page people (optional)
By default every new issue in the space pages your team. To narrow it, add a condition to Flow 1, between the trigger and the action. The usual choice is a JQL condition:
| To page for… | JQL condition |
|---|---|
| Urgent issues only | priority in (Highest, High) |
| One issue type | issuetype = Incident |
| A label | labels = page-oncall |
| A combination | issuetype = Bug AND priority = Highest |
Leave Flow 2 without conditions so any alerted issue still stops when it's done.
Responding to an alert
- Voice call: press 1 (or say "acknowledge") to stop the escalation. Press 2 to hear it again.
- SMS / WhatsApp: reply 1.
- Teams, Slack, push or the mobile app: tap Acknowledge.
- Incidents page: Acknowledge stops the alerts; Close removes it from your open list.
None of these change the issue in Jira — update the issue there as usual. When an issue is closed (in Jira or in JAMS) before anyone acknowledges, its Teams and Slack cards update to say so.
Different people for different spaces
Each connection has its own webhook URL and its own recipients. To page a different team per space, create one connection per space and point that space's Jira flows at its URL.
Troubleshooting
- Nothing arrives. Open the Jira flow's audit log. A failed web request shows the response from JAMS. Check the flow is turned on and the URL matches the one on the connection.
- The flow ran, but no alert. Make sure you pasted the JAMS body exactly — it must include
"issueId": "{{issue.id}}". A body without a real issue id is ignored. Also check alerting isn't paused. - Alerts stopped after working for a while. The connection shows a warning when no issue has arrived for 3 days. Jira Free and Standard plans cap Automation runs each month — if your site hit its limit, flows stop running until the next month. Keep conditions narrow.
- Alerted twice for one issue? It can't be — JAMS tracks each issue once per connection, even if the flow fires again or the issue is moved to another space.