Labels

this could be documentation, processes, etc.

This stage indicates that a ticket should be discussed and brainstormed. Testing and AC should be defined in this stage. Before a ticket leaves this state at least 1 Acceptance Criteria (AC) needs to be determined and the ticket must be able to be estimated. The next state is backlog::estimate.

Estimate the ticket. Tickets in this state should have clear acceptance criteria. If a ticket is estimated to be 3+ days work it shall return to the Discuss phase to be split. A ticket leaves this state when it is added to a sprint and the backlog::estimate label should be removed (as it's no longer on the backlog but rather in a sprint.)

This is the first stage for all new items on the backlog. The item may be very brief or just express an vague notion or concept. Tickets may stay here forever if it never gets refined. A ticket leaves this state when assigned a priority and move to backlog::discuss.

customer tickets

if an issue requires mapping to the MTTL

Label for tickets which the stucrew might be able to help tackle.

An issue that is currently being worked on

An issue that needs a second pair of eyes before merging its respective merge request

An issue that cannot be completed because of one blocker or another

Used to denote high level business value focused issues. These will be briefed at reviews and will likely have multiple issues linked to them for lower level implementation.