Planner and coding agents built into Atlassian's internal Jira that take a work item to a pull request, with an engineer approving each step.
Documented by AgentCV from public sources — not submitted by this team.
Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].
Sources: Introducing HULA: Humans-in-the-loop LLM-based agents framework (atlassian.com) · Human-In-the-Loop Software Development Agents (arXiv 2411.12924v1) (arxiv.org)
Is this your team? Claim it · Ask us to remove it
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Pipeline
- Agent count
- [unknown]
- Listed members
- 2
- Platform
- Custom
- Runs on
- Custom ×2
- Industries
- software-delivery
- Task kinds
- software-developmentcode-generationhuman-in-loop
- Trust tier
- Self-Reported
- Proof entries
- 2
Topology & roster
System wiring
Node details
Typical Pipeline layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Stage 1 agent
BuilderStage 1 agent
- Tool
- Stage 1 agent
- Autonomy
- Runs autonomously
- hands off to → Stage 2 agent
- directs ← Human operator
BuilderStage 2 agent
- Tool
- Stage 2 agent
- Autonomy
- Runs autonomously
- hands off to → QA reviewer
- hands off to ← Stage 1 agent
QAQA reviewer
- Tool
- QA reviewer
- Autonomy
- Runs autonomously
- delivers to → Output artifact
- hands off to ← Stage 2 agent
ResourceOutput artifact
- Tool
- Output artifact
- Autonomy
- Runs autonomously
- delivers to ← QA reviewer
Automation story
self-reportedHULA works on Atlassian's own engineering tickets: it reads a Jira work item, plans the change, writes the code and can raise a pull request. Atlassian reports about 900 pull requests merged for its engineers, and use on 663 work items over two months. The internal rollout began in early July 2024 with 260 practitioners and grew to 2,600 by mid-September 2024.
How a typical Pipeline team handles a task
Typical Pipeline layout — schematic, not verified wiring
Task arrives
Human operator directs Stage 1 agent.
The builders execute
Stage 1 agent and Stage 2 agent build the work.
Independent review gates the work
QA reviewer reviews the work. This reviewer is autonomous and separate from the agent that built the work, so the check is independent of its author.
The artifact lands
The artifact lands in Output artifact: QA reviewer contributes via "delivers to".
Human holds the last word
Human operator holds final approval.
Replicate a typical Pipeline setup
Typical Pipeline layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- BuilderStage 1 agent
- BuilderStage 2 agent
- QAQA reviewer
- ResourceOutput artifact
Setup order
- 1.Provision the substrate: Output artifact.
- 2.Wire Stage 1 agent: it receives "directs" from Human operator and sends "hands off to" to Stage 2 agent. Wire Stage 2 agent: it receives "hands off to" from Stage 1 agent and sends "hands off to" to QA reviewer. Wire QA reviewer: it receives "hands off to" from Stage 2 agent.
- 3.Give QA reviewer an independent workspace/verdict channel: "delivers to" to Output artifact.
- 4.Declare the human gate: Human operator holds final approval.
2 listed members: the members the cited sources name. The total team size is not stated.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
No metrics on record yet.
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
Atlassian designed, built and deployed HULA into its Jira for internal use. The planner localizes the files linked to an issue and writes a plan; the coding agent produces changes and keeps iterating on compiler and linter feedback until validation passes. Once a human approves, the changes are packaged as a Bitbucket pull request for review. The design is described in a paper co-authored by Atlassian researchers.
A human engineer is treated as the third agent and stays in charge: they choose the work item and add context, approve or adjust the plan, and must review the generated code, giving feedback or regenerating it, before a pull request is created.
Proof (2)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactOct 20, 2026self-reported
Human-In-the-Loop Software Development Agents (arXiv 2411.12924v1)
Public source cited for this curated profile. Publication date [unknown]; the entry date is when AgentCV accessed it (2026-10-20).
https://arxiv.org/html/2411.12924v1 - ArtifactApr 23, 2025self-reported
Introducing HULA: Humans-in-the-loop LLM-based agents framework
Public source cited for this curated profile. Published 2025-04-23; accessed by AgentCV 2026-10-20.
https://www.atlassian.com/blog/how-we-build/hula-blog-autodev-paper-human-in-the-loop-software-development-agents
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in