Jira
Connect Jira Cloud for two-way ticket sync. Status comes back without anyone updating it.
With Jira connected, OpsLyft creates issues in each team's project, writes the money at stake and a link back onto the issue, and syncs status both ways.
Connect Jira
Go to Tickets → Integrations and select + Connect, then Jira Cloud.
Sign in to Atlassian and choose your site, such as acme.atlassian.net. Approve the requested access.
Check the status mapping and field mapping.
Turn on the auto-create rules you want.
How sync works
| Direction | What syncs |
|---|---|
| OpsLyft → Jira | New issues, $ at stake, the OpsLyft link, due date from the SLA, and priority |
| Jira → OpsLyft | Status changes, mapped to OpsLyft states |
The Tickets header shows when Jira last synced and how many tickets are out of sync. Select Sync now in Integrations to force a sync.
Create a Jira issue from a ticket
On a ticket without a Jira issue, select + Jira. OpsLyft creates the issue in the team's mapped project.
Custom Jira statuses that aren't mapped are treated as In progress and flagged on the ticket.
Coming from v1
Your v1 Jira connection is still connected. In v2, sync is two-way.