New Savings Proposals: approve, test and roll back cost changesLearn more Sign in|Talk to a cloud engineer
Product tourGet a demo

Send savings work straight to Jira

Create a prefilled Jira issue from any recommendation, EOL finding or Atlas finding. CloudLens links the two, won't let anyone open a duplicate, and shows Jira's status next to its own.

Get a demoAll integrations
What you're watching
  1. 1
    Open Create issue on the top row

    Rightsizing the checkout-api node group to m7g.xlarge saves $3,140 a month and belongs to Checkout. Create issue opens the Jira form.

  2. 2
    Check the prefilled fields

    Project FINOPS, issue type Task, summary, savings, service, owner and the cloudlens and cost-savings labels are already filled in.

  3. 3
    FINOPS-218 is created

    The key appears in the Jira column, the recommendation moves to In Progress, and the activity feed shows Ana created it.

  4. 4
    Reconcile when Jira says Done

    Priya moves FINOPS-218 to Done. A banner flags that CloudLens still says In Progress, and Reconcile marks it Addressed.

Who does thisFinOps lead creating tickets, and the Checkout engineer working them in JiraWhat you getA recommendation becomes a Jira task with nothing retyped, and its status stays tied to that task.
Issues and epicsOne ticket, or an epic for a group of related findings
No duplicatesOnce a ticket exists, the button links to it
Both statuses shownJira's live status sits beside the CloudLens one
Comments carried overAtlas finding comments can post to the issue

Findings that live outside Jira rarely get fixed

Engineers plan their work in Jira. A finding in another console is one more place nobody checks.

Delivery

Work outside the tracker stalls

What usually happens: A rightsizing recommendation sits in a report. The owning team plans its sprint from Jira and never sees it.

How CloudLens resolves it: The issue is created in the team's project with savings and owner filled in, ready for the next planning session.

Resolved
Duplicates

Duplicate tickets waste time

What usually happens: Two people spot the same idle database and each open a ticket. One is closed as a duplicate after work already started.

How CloudLens resolves it: After the first issue is created, the button becomes a link to it. Nobody can open a second one from CloudLens.

Resolved
Reporting

Statuses drift apart

What usually happens: The ticket was closed two weeks ago, but the recommendation still reads Not Started and the month-end savings report is wrong.

How CloudLens resolves it: Jira's status is shown next to the CloudLens status. When they disagree, the row is flagged so someone reconciles it.

Resolved

Every field filled from the recommendation

Summary, savings, service and owner come from the recommendation itself. Pick a project and issue type or keep the defaults your admin set. Creating the issue moves the recommendation to In Progress, so the list shows what is actually being worked on.
  • Recommendations
  • EOL findings
  • Atlas findings
  • Epic bundles for related findings
  • Link back to CloudLens
What you're watching
  1. 1
    Pick the recommendation

    The highlighted row is the checkout-api rightsizing, worth $3,140 a month. Rows that already have an issue show its key, such as FINOPS-219.

  2. 2
    Fields arrive filled in

    The form carries project, issue type, summary, and a description with savings, service, owner and a link back to CloudLens.

  3. 3
    Status follows the ticket

    After Create issue, the row shows FINOPS-218 and In Progress. When Jira later says Done, the row is reconciled to Addressed.

Who does thisFinOps analyst or engineering manager filing work into a team's backlogWhat you getThe owning team gets a task it can plan, and the recommendation list shows the work as in progress.

Jira's status sits next to ours

CloudLens reads the live status and status category of every linked issue and shows them beside the recommendation. Neither one overwrites the other.

If Jira says Done while CloudLens still says In Progress, the row is flagged and a person decides. Moving a recommendation can also transition its Jira issue, using the status mapping your admin configured.

  • Live status and category
  • Mismatch flag
  • Admin-configured transitions
What you're watching
  1. 1
    CloudLens reads the live status

    FINOPS-218 moves across the Jira board from In Progress to In Review to Done, and the CloudLens card shows each change.

  2. 2
    The difference is flagged

    Jira says Done while CloudLens still says In Progress, so the sync field changes to Differs. Neither status is overwritten.

  3. 3
    Mark Addressed pushes to Jira

    A person clicks Mark Addressed. The Addressed to Done row in the status mapping lights up and the transition goes to Jira.

  4. 4
    Comments reach the issue

    A comment on an Atlas finding is posted to the linked issue, SEC-77, so the security discussion stays with the ticket.

Who does thisFinOps lead reconciling statuses, with the Jira admin who set up the transition mappingWhat you getJira and CloudLens end up agreeing, and every Addressed status was confirmed by a person.

Set up once by an admin

Enter your Jira base URL, a service account and an API token. The token is stored encrypted and never shown again. Choose a default project and issue type, then run Test connection before anyone creates a ticket.
  • Encrypted API token
  • Default project and issue type
  • Test connection
Jira integrationConnected
https://lumoraretail.atlassian.net
cloudlens-bot@lumoraretail.com
•••••••••••••••• (encrypted)
FINOPS
Task
Test connection Connection works

One recommendation, from report to Done

Lumora Retail's Checkout team plans two-week sprints in Jira. This is how a single rightsizing recommendation moved through that week.

ARAna RuizFinOps lead, Lumora Retail

Lumora Retail is a fictional company. The people, names and numbers are sample data.

    1
    Mon 09:40Not Started

    Picks the week's biggest recommendation

    Ana filters Recommendations to Not Started and sorts by savings. Rightsizing the checkout-api node group is worth $3,140 a month and belongs to the Checkout team.
    2
    Mon 09:44In Progress

    Creates FINOPS-218

    She clicks Create Jira issue. Project, issue type, summary and savings are already filled in. She adds a note about the Saturday change window and creates it. The recommendation moves to In Progress.
    3
    Mon 11:10

    The Checkout lead picks it up

    Priya sees FINOPS-218 on the sprint board and moves it to In Progress in Jira. CloudLens shows both statuses side by side, and they match.
    4
    Wed 16:25No duplicate

    Someone else tries to ticket it

    Marcus from Platform opens the same recommendation. The button now reads FINOPS-218 and opens the existing issue, so no second ticket is created.
    5
    Fri 14:05Mismatch flagged

    Jira reaches Done first

    Priya closes FINOPS-218 after the node group is resized. CloudLens flags that Jira says Done while the recommendation is still In Progress. Ana checks the new instance type and marks it Addressed.
Tickets filed twice, statuses out of sync?

See two-way Jira status in a demo

Get a demo

Every place work starts in CloudLens

Recommendations

Rightsizing, idle resources, commitments and storage, with savings and owner in the ticket.

EOL and deprecation

One ticket per finding, or one epic for every database still on an old engine version.

Atlas findings

Toxic combinations and exposures. Comments on the finding can post to the issue.

Already ticketed

If an issue already exists, CloudLens shows its key and link instead of creating another.

How the status sync works

For every linked issue, CloudLens stores Jira's live status and status category (to do, in progress, done) alongside the CloudLens status. Neither value replaces the other.

If Jira says Done but the recommendation is still In Progress, the row is flagged. Someone on your team reconciles it, because only a person should decide that a saving was addressed.

Moving a recommendation can transition its Jira issue, based on a status-to-transition mapping your admin sets up. If there is no mapping for that move, CloudLens says so rather than guessing.

Comments on an Atlas finding can be posted to the linked Jira issue, so the security discussion stays with the ticket where the fix is tracked.

Not Started → To DoIn Progress → Start ProgressAddressed → Done

Jira FAQ

The Jira base URL you enter in Settings, using a service account and an API token. We confirm your setup with you during onboarding.

Yes. It moves to In Progress, so the recommendation list reflects work that has started.

Yes. Epic bundles group related work, such as every database affected by the same end-of-life engine version.

CloudLens flags the mismatch between Jira's Done and its own status. The recommendation is not marked Addressed until someone on your team does it.

Ready to see CloudLens in action?

Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.