The issue tracker no longer reflects a task’s lifecycle

The status “task assigned to developer” now conceals an entire production pipeline.

What actually happens inside a single Jira status

01BriefingA person defines the task, constraints, and context.

02WaitingThe run is queued, waiting for compute, or working.

03PlanThe agent explores the project and proposes a solution.

04Plan reviewA person approves, changes, or rejects the plan.

05ImplementationThe agent writes code and runs checks.

06Review / QAA person accepts, adjusts, or rejects the result.

In Jira: “New feature—4× clan war · In Progress”

A lead can no longer understand the person’s true workload. Are they busy and not to be interrupted—or free and merely waiting for a long agent implementation that may run for five or six hours? Can they take a second task—or is the local runtime already full? Delegation is invisible, so the issue tracker cannot answer a basic management question: where is the work right now?

One Jira status · full production pipeline

Jira · HC‑4XWAR‑17In Progressnew feature · assigned to developer

under one statusexecution is hidden

Actual workSix distinct stagesagent · runtime · plan · implementation · QA

briefingqueueplanimplementationacceptance

Jira reports who owns the card, but not where the work itself is.