Work tracker sync

Your source of truth stays Jira Cloud

A Jira Cloud site is authorized with OAuth, so issues import, agents deliver work, and transitions, rich text, and comments stay current both ways.

Not open yetThe Jira integration is built and tested, and still cannot be connected. Opening it to other organizations waits on a data-handling declaration of ours, not on anything the provider has to decide. This guide is the contract it was built to.

Join the waitlist See the Jira example

Jira with Aestus

Keep the tool. Change what the team can see.

Teams whose source of truth is Jira usually cannot move it, and often should not. Finance, audit, support, and half the company's reporting already read from it. So Aestus connects to the Jira Cloud site instead of replacing it: projects and issues import, epics arrive as Aestus projects, sub-tasks stay children, and the work an agent does shows up where the rest of the business already looks.

Fidelity is where these connections normally disappoint, so the boundaries are stated up front. Status changes execute the transitions a project's workflow allows, so an issue never lands in a state its workflow forbids. Descriptions and comments convert between Atlassian Document Format and markdown under a policy that says what degrades and refuses a write it could not fully read — and after an import you are shown exactly which constructs read differently on the board. Assignees are bound by hand, because Jira exposes an account id and usually not an email, and guessing people is worse than asking.

The failure buyers have been burned by is a connection that stops without saying so — most often an expired webhook registration. Jira registrations expire after thirty days, so Aestus refreshes them on a schedule, shows their age on the integration, and re-reads changed issues on a sweep. Sprints and story points are kept alongside the issue so nothing is lost; this first version neither manages them nor shows them inside Aestus.

Good first workflows

Try one project first
Import a single Jira project, check the mapping against a dry run, and turn on outbound writes after.
Keep reporting intact
Leave sprints, story points, and epics in Jira so the dashboards the business reads keep working.
Return proof, not a status guess
Send the pull request and the executed transition back to the issue the request came from.

A complete Jira example, from trigger to proof.

The example names the people, task event, tool boundary, returned evidence, and acceptance state. The run row below it is a fixed product example, not customer data.

Example — fictional team and data. Not a live run or customer result.

Inside the connected tool

What the result looks like in Jira

The issue moves through a transition its workflow allows, and the delivery comment stays where the business already reports from.

Meridian Platform / PROJ-980 · Customer import hardening

PROJ-1042 · Story

Reject malformed currency separators on import

Aestus APP Comment

Delivered by the Aestus coding agent for Daniel Okafor. PR #241 is open with 19 passing import tests.

Linked work · Aestus PLAT-104 · run EXAMPLE-JR-01

Status

In Review

Moved by an allowed transition

Details

Assignee: Aestus coding agent
Reporter: Daniel Okafor
Sprint: Sprint 41
Story points: 3

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Deliver a Jira story while Jira stays the system of record

A story in a company-managed Jira project is assigned to an Aestus agent. Finance and audit keep reading Jira, and the delivery evidence arrives there.

TriggerPROJ-1042 is assigned to the Aestus coding agent

1
Daniel · Platform
Keeps the story where the business reads it
The epic, sprint, and story points stay in Jira. Aestus keeps them alongside the issue rather than managing or restating them.
PROJ-1042 · epic PROJ-980
2
Aestus sync
Imports the project pair after a dry run
The dry run reported the counts first; the epic arrived as an Aestus project and sub-tasks as children.
dry run · 214 issues previewed
3
Aestus coding agent
Opens the pull request and records the run
The repository, checks, cost, and failure state stay attached to the card that requested them.
EXAMPLE-JR-01 · PR #241
4
Aestus sync
Transitions the issue and comments with attribution
The status moves through a transition the project's workflow allows, never a forced state.
In Progress → In Review · attributed

Example — fictional team and data. Not a live run or customer result.

Deterministic product example — not a production run

Deliver the imported Jira story

Example run		Runtime	Outcome
EXAMPLE-JR-01	Aestus coding agent	aestus	Completed	$0.02	71.0s

Tokens in / out: 9,400 / 500
Failure code: —
Agent: coding-agent

Example source: lib/marketing/integration-run-examples.ts

Example run cost

$0.0198 in the worked example on this page

The figure is a fixed illustration drawn from comparable Aestus coding-agent runs, not a measurement of a Jira sync that has run. It stands for one agent run of 9,400 input tokens, and keeping the issue current is part of that run rather than a second charge.

Set it up in four steps.

Follow the real Jira connection path. Provider steps link to the provider documentation. Aestus steps name the contract they follow.

01
Authorize the Jira Cloud site
An organization admin opens Settings, Integrations, then Jira. There is no Marketplace listing to install and no Forge app to deploy, and one authorization picks the site to bind.
Aestus contract: docs/jira-sync-setup.md
02
Pair projects and epics
Each pair names one Jira project. Epics arrive as Aestus projects and sub-tasks stay children, through the same parent field for team-managed and company-managed projects.
Aestus contract: docs/jira-sync-setup.md
03
Bind Jira accounts to people
Jira usually hides email addresses, so assignee mapping is its own screen. Unmapped assignees land unassigned with a note instead of a guess.
Read the provider docs
04
Preview the import, then run it
The dry run reports what it would create without writing. You run it for real once the counts look right.
Aestus contract: docs/jira-sync-setup.md

The boundary stays visible while the work moves.

See what Jira can do, where a person still decides, and what Aestus records for every governed run.

Where control lives

Workflows keep their authority

Aestus changes a status by executing a transition the project allows. It never forces a status a workflow would refuse.

Site access stays administrator-owned

The connection is bound to one Jira Cloud site by its immutable cloud id, authorized once, with the granted scopes recorded.

Two-way writes start when you say so

A project pair runs import only until the team trusts the mapping, then moves to two-way without a reconnect.

What Aestus records

What crossed, in normalized form

Rich text moves between Atlassian Document Format and markdown under a written conversion policy, and both sides are compared as normalized content, never byte for byte. After an import you get the list of constructs that could not be reproduced exactly, so nothing degrades out of sight.

Connection health, not silence

Webhook age, registration state, sweep results, and re-auth needs are shown, because an integration that quietly stopped is worse than one that reports an error.

Delivery evidence on the card

The pull request, checks, and run cost already stay attached to the task that requested them; the comment posted back to Jira joins them.

Questions teams ask

Can we use this today?

Not yet, and not because it is unwritten. The sync is built and tested end to end: authorization, project pairing, transitions, custom-field discovery, webhook registration, backfill, reconciliation, and the settings screens. What is outstanding is ours, not Atlassian's — switching the app on for organizations other than ours means filing a personal-data declaration and attesting we have implemented Atlassian's Personal Data Reporting API. There is no review queue on their side. Until we have filed it, this guide is the contract you can hold us to.

Do we need a Marketplace or Forge app?

No. Aestus connects to Jira Cloud with a standard OAuth 2.0 authorization, so there is nothing for an admin to install on the Atlassian side.

Does our formatting survive?

Descriptions and comments convert between Atlassian Document Format and markdown under a policy that names what degrades, such as panels and media, and refuses a write it could not fully read rather than deleting what it did not understand.

See all integrations See the security controls

Start with one Jira run.

Bring one real run. Map its actors, boundary, evidence, cost, and acceptance step.

Talk to us

Your source of truth stays Jira Cloud

A Jira Cloud site is authorized with OAuth, so issues import, agents deliver work, and transitions, rich text, and comments stay current both ways.

Example — fictional team and data. Not a live run or customer result.

Concrete workflow example

Deliver a Jira story while Jira stays the system of record

A story in a company-managed Jira project is assigned to an Aestus agent. Finance and audit keep reading Jira, and the delivery evidence arrives there.

TriggerPROJ-1042 is assigned to the Aestus coding agent

1
Daniel · Platform
Keeps the story where the business reads it
The epic, sprint, and story points stay in Jira. Aestus keeps them alongside the issue rather than managing or restating them.
PROJ-1042 · epic PROJ-980
2
Aestus sync
Imports the project pair after a dry run
The dry run reported the counts first; the epic arrived as an Aestus project and sub-tasks as children.
dry run · 214 issues previewed
3
Aestus coding agent
Opens the pull request and records the run
The repository, checks, cost, and failure state stay attached to the card that requested them.
EXAMPLE-JR-01 · PR #241
4
Aestus sync
Transitions the issue and comments with attribution
The status moves through a transition the project's workflow allows, never a forced state.
In Progress → In Review · attributed

Example run

Runtime

Outcome

EXAMPLE-JR-01

Aestus coding agent

aestus

Completed

$0.02

71.0s

Questions teams ask

Can we use this today?

Do we need a Marketplace or Forge app?

No. Aestus connects to Jira Cloud with a standard OAuth 2.0 authorization, so there is nothing for an admin to install on the Atlassian side.

Does our formatting survive?

Your source of truth stays Jira Cloud