Ticket integrations
Connect Jira, Slack, Linear, and ServiceNow, map teams to projects, and choose which findings open tickets automatically.
Open Tickets → Integrations (or Integrations at the top of the Tickets page). The header shows how many tools are connected and that sync is two-way.
Connections
| Column | Meaning |
|---|---|
| Connection | Jira Cloud, Slack, Linear, or ServiceNow |
| Site | The connected site, such as acme.atlassian.net or acme.slack.com |
| Health | Healthy or Not connected |
| Last sync | When OpsLyft last synced |
| Synced · 30 d | Items synced in the last 30 days |
| Actions | Settings, Sync now, or Connect |
Select + Connect at the top to add a tool. Setup guides: Jira, Slack, Linear and ServiceNow.
Jira project mapping
Map each team to the Jira project where its new issues are created.
| Team | Project |
|---|---|
| payments | PAY |
| growth | GRW |
| platform | FIN |
| ai-platform | AIP |
| data-eng | DATA |
Teams come from your owner tag or allocation.
Jira status mapping
Status maps Jira's states to OpsLyft's, both ways.
| Jira | OpsLyft |
|---|---|
| To Do | Open |
| In Progress | In progress |
| In Review | In review |
| Done | Done |
| Won't Do | Won't do |
Jira statuses that aren't mapped are treated as In progress and flagged on the ticket. Map custom workflow states to avoid this.
Jira field mapping
What OpsLyft writes onto each Jira issue:
| OpsLyft field | Jira field |
|---|---|
| $ at stake | A custom field, such as customfield_10041 · Savings |
| Source link | A custom field, such as customfield_10042 · OpsLyft URL |
| SLA | Due date |
| Priority | Priority |
Auto-create rules
Auto-create rules decide which findings become tickets without anyone clicking. Everything else needs a click: + Ticket on the opportunity, anomaly, or budget. Each rule shows how many tickets it created in the last 30 days.
| Rule | Condition | Goes to | Priority | SLA |
|---|---|---|---|---|
| Opportunities ≥ $10K/mo → ticket | Saves ≥ $10K/mo | Team project | Medium | — |
| High-severity anomalies → ticket | Impact ≥ $200/day | Team project | High | 1 day |
| Budget exceeded 100% → ticket | Any budget crosses 100% | FIN | Medium | 3 days |
| Medium anomalies → ticket | Impact ≥ $50/day | Team project | Medium | — |
Use the toggle on each rule to turn it on or off. The medium-anomaly rule is off by default.
Slack
| Event | Where it goes |
|---|---|
| Ticket created | #finops-alerts and the team's channel |
| SLA breach | A DM to the owner and #finops-alerts |
| Weekly digest | #finops, Monday 09:00 in your timezone |