Your tracker has no private draft state, and it shows

Description and use

Adding a private draft state to issue trackers reduces premature visibility of ideas, lowers revision costs, and clarifies when a task is truly ready for the team.

Problem

Issue trackers lack a private draft state, causing ideas to become visible tasks prematurely and leading to costly revisions and miscommunication.

Outcome

Introducing a private draft state reduces premature visibility, lowers revision costs, and clarifies when a task is truly ready for the team.

Workflow

• Capture idea as a one-line note or ticket in draft state
• Edit and refine scope, acceptance criteria, and context privately
• Attach necessary documentation and context
• Perform a written acceptance check
• Move ticket from draft to public board
• Team members can now comment, estimate, and start work
• If needed, revise in draft before re-publishing
• Track progress through standard states (In Progress, Done)

Evidence

Rewriting the scope of a private draft costs nothing. Rewriting the scope of a published ticket means notifying whoever commented, correcting whoever started, and re-litigating whatever was already negotiated.

Source