GitLab

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a < type of user >, I want < some goal > so that < some reason >.

Technical dept story: refactoring, optimization, documentation, unfinished implementation, tests etc.

Large body of work that can be broken down into a number of smaller stories

A developer can start working on this task

The issue is fixed/implemented and is waiting for approval from the QA team.

Postponed until some condition is met (see issues comments)

New suggestion to build a feature/user story, product enhancement, bug etc.

The issue is in development.

Additional information needed to proceed with the issue

The issue is being discussed by the team/community

The issue is under peer code review.

The defect cannot be reproduced.

The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.

The defect affects minor functionality or non-critical data. It has an easy workaround. Example: A minor feature that is not functional in one module but the same task is easily doable from another module.

The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult. Example: A feature is not functional from one module but the task is doable if 10 complicated indirect steps are followed in another module/s.

The defect affects critical functionality or critical data. It does not have a workaround. Example: Unsuccessful installation, complete failure of a feature.