Integration: ticketing and approvals

Jira work tracking AI cost on every story

Argent Strategic Intelligence books each AI agent's spend to the Jira story it worked on, rolls it up, holds work at its cap, and writes the cost and a signed summary back to Jira.

01 / INTEGRATION: TICKETING AND APPROVALS

AI spend on the Jira story it served

AI agents now write code, tests and documents against real work items, and their bill usually arrives as one number at month end. Argent connects to Jira and books every agent's AI spend to the story it worked on.

  • Your Jira projects, epics and stories appear in Argent's Work catalog, kept in step with Jira.
  • Each request that goes through Argent is priced on Argent's signed ledger and booked to the story the agent declared, then rolled up through the epic to the project.
  • A budget can sit on the story, the epic or the project. At the cap, the work waits for its budget owner.
  • The cost can be written back into Jira, so the story itself shows what its AI work cost.
02 / INTEGRATION: TICKETING AND APPROVALS

What Argent does with Jira

StepWhat happens
Sync the boardArgent reads the projects, epics and stories on the boards you choose into its Work items, picking up where the last read stopped. Jira wins on state: the sync reads and never overwrites.
Book the spendIn ADE, the Argent Development Environment, the developer picks the story when launching a session, and the agent can declare the story it is on with a tool. Each sub-agent's spend is kept separate. Argent books the session's priced spend to that story, once.
Cap itAn admin sets a cap on a story, epic or project, with a warning at 80 percent. At 100 percent, set to Pause, the next prompt of every ADE session on that work is held until the budget owner chooses Raise cap or One-time overage.
Write the cost backA cost value on each synced story, equal to its lifetime AI spend and rewritten only when it changes.
Write the work backOn commit, ADE drafts one summary comment (what changed, which files, the cost of that stretch). The developer approves it, Argent removes secrets, signs it and posts it to the story. Closing the story in ADE can close it in Jira too.
03 / INTEGRATION: TICKETING AND APPROVALS

How the cost shows up in Jira

Each synced story can show its lifetime AI spend inside Jira.

Argent writes the cost into your own custom Number fields: you create them in Jira and name them in the connection, because Argent does not hold the rights to create fields. A story or task carries its own cost; an epic carries its own cost and the total of everything under it.

  • Values are absolute, never increments, so a missed run cannot double-count.
  • A field or permission Jira refuses shows as a cost error on the connection, with a fixed plain sentence and a signed row, never silently.
  • Cost write-back has its own switch per connection.
04 / INTEGRATION: TICKETING AND APPROVALS

How it connects

Argent talks to Jira's API over HTTPS, as the Atlassian service account.

  • Credential: an Atlassian service account (created under Atlassian Administration, Directory, Service accounts) with an API token or OAuth 2.0 credential, given one role per project with Browse Projects, Edit Issues (needed for the cost fields), Transition Issues and Add Comments, plus Browse users and groups so Argent can match people by email.
  • No secret in Argent's database. The credential stays in your vault and Argent stores a reference to it. Works with HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur or Infisical.
  • Guarded calls. Every call goes through Argent's protected HTTPS client, which refuses private addresses and redirects to other hosts. Calls go to your Jira Cloud site (for example your-site.atlassian.net) or Atlassian's API gateway api.atlassian.com.
  • Bounded sync. Each run reads a capped amount, so a misbehaving server cannot stall Argent or fill its database.
  • Plain errors. Failures are stored as fixed codes and sentences; Jira's own response text is never kept.
05 / INTEGRATION: TICKETING AND APPROVALS

What you configure

  1. Create the Jira credential: an Atlassian service account (created under Atlassian Administration, Directory, Service accounts) with an API token or OAuth 2.0 credential, given one role per project with Browse Projects, Edit Issues (needed for the cost fields), Transition Issues and Add Comments, plus Browse users and groups so Argent can match people by email. Store it in your vault.
  2. Connect Jira in the Argent console under Work, Trackers, with the address and the vault reference.
  3. Pick the boards to sync. Argent maps Jira's project, epic and story or task to its own project, feature and story levels.
  4. Turn on the write-backs you want. Every switch ships Off: Summary comment, and Closed: move to a column you pick (default Done).
  5. Name the cost fields and switch cost write-back on for the connection.
  6. Set budgets on the work items that need a cap, and say whether 100 percent pauses or only alerts.

Spend is booked for agents that work through Argent; ADE is where the developer picks the story and the agent declares it.

06 / INTEGRATION: TICKETING AND APPROVALS

Signed, and Jira stays in charge

Every write-back is signed in Argent's ledger before it is posted, and refused if the ledger is down.

  • The Tracker sync trail lists each write: the person, the Jira story, COMMENT, STATUS CHANGE or CLOSE, and POSTED, RETRYING or REFUSED BY TRACKER.
  • Each comment ends with Posted by Argent on behalf of <person>, agent <agent>. and its record id.
  • If someone already moved the story in Jira, the tracker wins: Argent leaves it as Jira has it.
  • No agent can lift a hold or approve its own comment: every write an agent asks for waits for its human owner.

Hand the trail to an auditor with one-click audit evidence.

07 / INTEGRATION: TICKETING AND APPROVALS

Where this fits

Browse all integrations.

Connects with
  • Jira