Issue tracking
Attach the running AI cost to the Linear issue it belongs to.
Each Linear issue can carry the AI cost of the branch named after it. Lineman looks for a Linear issue identifier, such as ENG-123, in the name of the branch the work happened on, and puts the running total on that issue as an attachment in the sidebar. Nobody fills in a field or picks a ticket, and the figure covers everyone who worked on the branch rather than one person.
Use Linear's copy-branch-name button and the branch already carries the issue identifier, so the spend on it reaches the issue without a manual linking step. There is no custom field to add and no ticket picker to work through. A branch called fix-login-bug has no identifier in it, so its cost stays in Cost Explorer and never reaches an issue.
The cost lands as an attachment in the issue sidebar rather than a comment, so it does not bury the discussion. The figure is cumulative for the linked branch and shown in US dollars, never cents, so it compares directly with Cost Explorer. Updates replace the attachment rather than stacking, and it is refreshed on a scheduled run, so cost recorded a few minutes ago will not be there yet.
Two people on the same branch produce one combined number, so the issue shows what the work cost rather than what each person spent. You choose which Linear teams this applies to: the integration page lists your teams switched off, and nothing is written to any issue until you switch one on.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations