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.

The customer's proposal has been reviewed and rejected for reasons that will be written down in the issue's comment section.

if an issue requires mapping to the MTTL

This label is specifically for the JQR presentation from the MTTL

Relating to KSATs (add, remove, modify) but not linking/mapping. Use mttl::rel-link for mapping issues.

Communicating with with the customer and create KSATs that fit the customer's vision of this requirement.

Review KSAT requirements in specified work-role and if they fit in the overall picture. This will include approval and merge into production.

types of metrics and reporting displayed

Issues relating to the pipeline

specifically for rel-link changes and additions

mttl tool scripts

Used for visualization requirements (e.g. Kumu.io)