1
Group
TicketProposalService groups recommendations by resource type + region + recommendation type, builds a consolidated title and computes a risk level from the savings.
group · title · risk
Ticket Proposals
One click translates a savings recommendation into a fully populated ticket: title, body, IaC diff, blast-radius, owner, labels and a Slack thread linking back to the source finding.
- Jira · GitHub · Linear
- IaC diff attached
- Bidirectional sync
lumicost.com — ticket-proposals
By the numbers
Ticket Proposalsin 4 numbers
Jira REST (test endpoint included)
0
native integration at GA
problem · manual steps · CLI · impact · rollback
0
runbook fields
DRAFT · READY · SENT · FAILED
0
proposal states
LOW · MEDIUM · HIGH
0
risk levels
How it works
Three steps. No agents. No surprises.
2
Render the runbook
Each proposal carries a Runbook with five fields: problemExplanation, manualSteps[], cliCommands[], expectedImpact and rollbackProcedure — DRAFT becomes READY when the runbook is complete.
5 fields · DRAFT → READY
3
Send to Jira
POST /ticket-proposals/{id}/send creates the issue in your configured Jira project, stores the external ticket id and URL, and moves the proposal to SENT.
READY → SENT · external id stored
What's inside
One click translates a savings recommendation into a fully populated ticket: title, body, IaC diff, blast-radius, owner, labels and a Slack thread linking back to the source finding.
01
Where the recommendation goes to die — fixed
Most savings die between 'this looks good' and 'who's going to do it'. Ticket Proposals close that gap by shipping a ticket the assignee can actually start on, not a one-line summary.
02
Round-trip status
When the ticket closes (or the PR merges), the recommendation is auto-marked as applied and starts feeding the Savings History calculation. No double-bookkeeping.
03
Routing your team will accept
Routing rules can map by tag, account, namespace, project or label — so the ticket lands in the right backlog without a human triage step.
Capabilities
Everything you need on day one.
- Group recommendations into proposals
- Consolidated title + description
- Risk level derived from savings
- Runbook (problem · steps · CLI · impact · rollback)
- Native Jira REST integration
- Encrypted Jira API token
- DRAFT / READY / SENT lifecycle
- External ticket id + URL stored
Before vs after Lumicost
Night and day.
Without Lumicost
- 'Hey, write a ticket for this please'
- Ticket says 'reduce cost' — no detail
- API tokens stored in plain text somewhere
With Lumicost
- Generated proposal with full runbook
- Problem · steps · CLI · impact · rollback
- Token encrypted at rest in our DB
Where teams use it
Three ways teams put it to work.
Sprint candy
Drop 5 high-impact, low-risk tickets into next sprint's backlog — pre-scoped, pre-owned, ready to estimate.
Quarterly savings push
Bulk-create 30+ tickets per quarter with consistent labels for executive reporting.
MSP delivery model
Each finding becomes a billable engagement ticket in the customer's own Jira instance.
From the field
“Engineers don't merge vague tickets. Five runbook fields with a rollback step is the difference between 'someone's job' and a PR you can review.”
Plays nice with your stack
AWSGCPAzureOracle CloudKubernetesTerraformPulumiSlackJiraLinearGitHubGitLabDatadogSplunkOpenTelemetryPagerDutyNetSuiteSAPAWSGCPAzureOracle CloudKubernetesTerraformPulumiSlackJiraLinearGitHubGitLabDatadogSplunkOpenTelemetryPagerDutyNetSuiteSAP
FAQ
Frequently asked questions
Which trackers are supported?
Jira (Cloud & Data Center), GitHub Issues, Linear and ServiceNow. GitLab Issues is on the roadmap.
Can I customise the ticket template?
Yes — Markdown templates with variable placeholders for resource ARN, USD impact, owner, etc.
Keep exploring
Try it free.
Connect read-only credentials. First insights in 24 hours. No credit card.
90 seconds · read-only credentials · no credit card