Cost visible on the request
The running total sits on the work item view your agents already use, so the cost of a request is in front of them while they triage it. There is no separate report to open.
Issue tracking
Lineman and Jira Service Management
Write each service request's AI cost onto the ticket, using your existing Jira connection.
What this gets you
Lineman writes the cumulative AI cost of the work behind a service desk request, in US dollars, onto an "AI Spend (Lineman)" number field on that request, and refreshes it hourly. Whoever picks the ticket up sees what it has cost so far without opening Lineman. It runs on the same Atlassian connection as the Jira integration, and you choose which service desks it writes to. On a service desk you add the field yourself, once to each work type you track, because service desks use their own screens.
What people use it for
Attribute spend by request key
Request keys are ordinary Jira keys. Name a branch after the request or mention its key, for example ITSM-123, and the cost of that work lands on that request. Attribution works exactly as it does for Jira Software, with no separate rule for service desks.
Keep the figure internal
The field goes on the work type, not on the customer portal form, so a reporter does not see it unless you add it to their request type. Every service desk stays switched off until you tick it, so connecting Atlassian does not start writing to a customer-facing queue.
More in Issue tracking
Set up Jira Service Management
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