A bug with a known cause/source (usually triggered by a recent merge)

A loss of functionality or outage that negatively affects a significant portion of users and requires urgent attention

Improve existing code without adding new functionality

Community members are requested to solve this problem in exchange for a reward

Issues that have been proposed but are not yet validated

The issue depends on the completion on another issue in order to proceed.

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 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

Tasks that are ready for developers to take from

Used when a Superhero is made

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

Task related to Pro customers

Issues related to Plus customers

Issues related to Hosting/Node customers