Cost on the issue itself
The spend for an issue sits in a field on that issue, so a lead or product manager reading the ticket sees the figure in place. Ticking a project in the picker is what starts the write-back, on the next hourly run.
Issue tracking
Lineman and Jira
Write each issue's cumulative AI cost onto the Jira ticket as a field.
What this gets you
Lineman writes each issue's cumulative AI spend onto the Jira issue itself, into a number field named exactly "AI Spend (Lineman)", refreshed hourly. Anyone who opens the issue sees what the work has cost so far without opening Lineman. On company-managed (classic) projects Lineman creates the field and adds it to the issue screen for you. Team-managed (next-gen) projects manage their own fields, so the field is added once to each work type you track.
What people use it for
Attribution from the issue key
Name the branch after the issue, or mention its key, for example ABC-123, and the spend from that work is attributed to that issue.
One cumulative figure, refreshed hourly
Each tracked issue carries a single cumulative total: every cost recorded against it so far, rewritten on each hourly run, or when you press Re-check on the integration page. If a write-back starts failing, the integration status page shows a note with guidance for the affected project.
More in Issue tracking
- GitHub IssuesPost the AI cost of an issue as a comment on the issue itself.
- LinearAttach the running AI cost to the Linear issue it belongs to.
- Azure DevOpsWrite AI cost onto the linked Azure Boards work item.
- ClickUpShow each ClickUp task's AI cost on the task, keyed off the id already in your branch names.
Set up Jira
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideLooking for something else?
Every integration in one place, searchable by name and filterable by what it does.
View all integrations