Tickets
The work that comes out of opportunities, anomalies, and budgets, synced two ways with Jira and verified against the bill.
Tickets is where findings become work. Every ticket links back to the opportunity, anomaly, or budget that raised it, shows the money at stake, and syncs two ways with Jira. When a ticket closes, OpsLyft checks the bill to confirm the saving.
The header shows sync health, such as Jira synced 2 min ago · 3 not in sync.
Summary tiles
| Tile | Shows |
|---|---|
| Open | Open tickets, how many breached their SLA, and money at stake per month |
| In progress | Tickets being worked on, how many are in review, and money at stake |
| Closed · this quarter | Tickets closed, how many were won't do, and how many have a verified outcome |
| Money saved · monthly | Savings verified in billing from closed tickets, and more in flight |
Select Range to change the period.
List and board
- List groups tickets by Source (Optimisation, Anomaly, Budget) by default. Change it with Group.
- Board shows tickets in columns by state.
| Column | Meaning |
|---|---|
| Key | The OpsLyft ticket ID, such as TKT-112 |
| Ticket | Title, plus badges such as verified −$4.1K/mo, accepted risk, or resolved · level normal for 14 d |
| Team | The owning team |
| $ at stake | Savings per month, excess per day, or amount over budget |
| Owner | The person responsible, or Assign |
| State | Select a state to advance it |
| Due | Time to the SLA, SLA breached · 26 h, or when it was last updated |
Select + Jira on a ticket to create the issue in the team's mapped Jira project.
Create a ticket
- Select + Ticket on any opportunity, anomaly, or budget.
- Select + Ticket at the top of the Tickets page to create one by hand.
- Or let auto-create rules do it.
Filter and export
Use the Ask bar (for example high-priority anomaly tickets not in Jira), Filters, and Group. Select Export CSV at the bottom of the list.