Issues that require planning work. All issues in this state MUST use the DoR (default) template. The next stage is Status::Scheduling.

Issues that are now waiting for QA

Tasks that have met the Definition of Ready (DoR) criteria - https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Merge request has been reviewed and approved and is ready to be merged. Do NOT apply to MRs with WIP status

Merge request has been reviewed, but needs to be changed before it can be approved and merged

Awaiting peer review before being made live

Issues that are ready for development but have still to be signed off as per the Definition of Ready (Tasks that have met the Definition of Ready (DoR) criteria - https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor). Issues in this state MUST be sufficiently build out. The next state is "Status::Ready For Devs".

Evaluate the issue and dictate the future of the workflow

Used when a Superhero has been accepted by a developer. The issue should also be assigned at this stage.

Used when a Superhero is resolved

Used when a Superhero is made

Technical Debt

Dead end: bug was reported but can't be reproduced

Use for Technical Analysis, Spike tasks, Investigation etc.