Ticket cost reportingBuilt for

Claude Code

Your AI spending, assigned to the ticket

Finance asks what the AI budget went on, and engineering has no answer that survives scrutiny. Lineman prices every Claude Code session and writes the running total onto the ticket itself, so the breakdown by ticket, repository and developer is already there when the question comes - without anyone tagging, timing or filing anything.

Book a demo Start for free

A walkthrough on your own setup. Or start on the free tier, no card.

Works with your tracker

Jira

Linear

GitLab

GitHub Issues

Azure Boards

ClickUp

Jira Service Management

Write-back cadence: Hourly
Developer effort: One-line install

The gap

Your AI invoice has one line on it.

One number, once a month, for the whole company. Finance asks what the checkout rewrite cost. Engineering asks whether the agent earns its keep on small tickets. Neither question can be answered from a bill that has never heard of a ticket.

The provider console stops at the API key

It knows keys, models and dates. It does not know your repositories, your people, or your backlog.

Per-seat maths is not attribution

Dividing the bill by headcount tells you what people cost. It says nothing about what the work cost.

By the time you can see it, it is spent

A line item at month end cannot change a decision that was taken three weeks earlier.

Who it answers

One number, three different questions.

The same attribution answers the engineering question, the finance question and the board question. They are not the same question.

Engineering leads

Know which work is expensive while you can still act on it

Spend lands on the ticket, the branch and the person, so a capacity conversation uses numbers instead of impressions, and an expensive refactor is visible in week one rather than at month end.

Finance

An invoice you can actually break down

AI spend attributed to tickets, repositories, developers and cost centres, exported in a FOCUS-conformant dataset for whatever you already run. One line on a bill becomes a set of lines you can allocate and forecast.

Founders and execs

The cost of a feature, not the cost of a month

Ask what the checkout rewrite cost, and get an answer with the work behind it. The same view surfaces spend that should not have happened at all.

Cost reporting, including the ticket breakdown, is on the free tier. Alerts and budgets are the Pro part.

ISO 27001 + 27701 accreditation in progress
No prompt or source code leaves your machine
UK company, DPA available

See pricing Security and compliance

In the dashboard

The same spend, grouped your way.

The number on the ticket is one view of the data. In Cost Explorer the same spend regroups by ticket, developer, repository, branch, model or cost centre, over any date range you choose.

The Cost Explorer Browser view for tickets: spend over time stacked by ticket, above a sortable table of every attributed ledger entry in the window with its ticket, developer and cost. — Spend over time per ticket, and under it every attributed entry behind those totals, with the ticket and the developer on each. Sort it, scope it by dragging across the chart, or regroup it by developer to see the same period as a team view.

On the ticket

It lands as a field on the ticket.

AI Spend USD (Lineman) is a genuine Jira number field, so it sorts, filters and reports through JQL like any other. On company-managed projects Lineman creates it for you; on team-managed ones somebody adds it to the work type once.

MER-184Move the pricing page onto the shared plan matrixIn Progress

Details

Assignee: Sam Rivera
AI Spend USD (Lineman): 412.87
Parent: None
Due date: 12 Aug 2026
Labels: None
Team: Payments
Reporter: Ana Costa

An illustration of the Details panel, not a screenshot. The value is a plain number because that is what a Jira number field renders, which is why the unit is in the field name.

How it works

Three steps, and no new process.

No timesheets, no tagging, nothing for a developer to remember.

The session is priced as it runs

The plugin records every Claude Code session with what it cost and the repository, branch and commit it ran on.

The ticket key comes off the branch

A branch called feat/LIN-3570-ticket-costs resolves to LIN-3570. The plugin, the branch convention and the dashboard share one derivation, so the branch name your team already writes is the entire configuration. Where branches carry no key, a mapping rule fills the gap.

The total lands on the ticket, hourly

Once an hour, every tracked ticket whose total has moved is updated in your tracker. Tickets whose number has not changed are left alone, so the issue history stays readable.

git branchfeat/LIN-3570-ticket-costs

ticketLIN-3570$412.87

The branch you already named is the whole configuration.

Trackers

Where the number lands.

What each tracker gets you, and what you can turn on today. Request access means built and staff-tested against the real service, not yet released to everyone.

Tracker	What you get	Status
Jira	Every issue carries its own AI cost, in a real number field. Sort by it, filter on it and report it through JQL like any other Jira field.	Available
Jira Service Management	The same field on a service-desk request, so support work is costed alongside delivery work. You choose which desks are written to.	Request access
Linear	The cost sits in the issue sidebar as an attachment, updated in place rather than stacking up.	Available
GitLab issues	A note on the issue that is edited each hour rather than re-posted, so the discussion stays readable.	Available
GitHub Issues	A comment on the issue, edited in place. Totals are scoped per repository, because issue #123 is only unique inside one.	Request access
Azure Boards	A custom field on the work item, keyed on the AB#123 branch and commit convention your team already uses.	Request access
ClickUp	A comment on the task, edited in place. ClickUp has no API to create a custom field, so a comment is the only surface that works without per-list setup.	Request access

Jira
Every issue carries its own AI cost, in a real number field. Sort by it, filter on it and report it through JQL like any other Jira field.
Available
Jira Service Management
The same field on a service-desk request, so support work is costed alongside delivery work. You choose which desks are written to.
Request access
Linear
The cost sits in the issue sidebar as an attachment, updated in place rather than stacking up.
Available
GitLab issues
A note on the issue that is edited each hour rather than re-posted, so the discussion stays readable.
Available
GitHub Issues
A comment on the issue, edited in place. Totals are scoped per repository, because issue #123 is only unique inside one.
Request access
Azure Boards
A custom field on the work item, keyed on the AB#123 branch and commit convention your team already uses.
Request access
ClickUp
A comment on the task, edited in place. ClickUp has no API to create a custom field, so a comment is the only surface that works without per-list setup.
Request access

Repository, branch and developer attribution also works with GitHub, GitLab and Bitbucket, whether or not you use their issue tracker.

The honest part

What it does not do.

Four things worth knowing before you install it, rather than after.

The ticket number is hourly, not instant
Spend appears in Cost Explorer as it happens. The write-back to your tracker runs once an hour, so a ticket you are working on right now can be up to an hour behind.
A ticket has to be derivable
If a branch carries no ticket key and no mapping rule matches, the spend is still counted and still attributed to the repository and the developer. It simply has no ticket to land on.
Team-managed Jira needs the field added once
Jira's public API cannot add a field to a team-managed project on your behalf, so somebody with project admin adds AI Spend USD (Lineman) to the work type once. Company-managed projects are automatic.
It sees the sessions Lineman is installed for
A developer who has not installed the plugin contributes nothing to the total. The number is a floor on what a ticket cost, never an estimate above it.

Your AI spending, assigned to the ticket

Your AI invoice has one line on it.

The provider console stops at the API key

Per-seat maths is not attribution

By the time you can see it, it is spent

One number, three different questions.

Know which work is expensive while you can still act on it

An invoice you can actually break down

The cost of a feature, not the cost of a month

The same spend, grouped your way.

It lands as a field on the ticket.

Three steps, and no new process.

The session is priced as it runs

The ticket key comes off the branch

The total lands on the ticket, hourly

Where the number lands.

What it does not do.

The ticket number is hourly, not instant

A ticket has to be derivable

Team-managed Jira needs the field added once

It sees the sessions Lineman is installed for

Questions people actually ask

Put the AI bill on the ticket.

Your AI spending, assigned to the ticketrepositorydeveloperbranchcost centresessionticket

Your AI invoice has one line on it.

The provider console stops at the API key

Per-seat maths is not attribution

By the time you can see it, it is spent

One number, three different questions.

Know which work is expensive while you can still act on it

An invoice you can actually break down

The cost of a feature, not the cost of a month

The same spend, grouped your way.

It lands as a field on the ticket.

Three steps, and no new process.

The session is priced as it runs

The ticket key comes off the branch

The total lands on the ticket, hourly

Where the number lands.

What it does not do.

The ticket number is hourly, not instant

A ticket has to be derivable

Team-managed Jira needs the field added once

It sees the sessions Lineman is installed for

Questions people actually ask

Put the AI bill on the ticket.

Your AI spending, assigned to the ticket