Designates that the isssue belongs to the API.
Designates that the isssue belongs to the backend.
Issues where further work is prevented by a dependency.
Issues that prevent further work.
A problem which impairs or prevents the functions of the product.
Designates that the isssue belongs to the build process.
Issues that are necessary but less impactful for our users.
The issue is ready to be taken.
Designates that the isssue belongs to the general product.
Upgrade of dependency. Typically handled by automated tooling.
Issues that affect the development process.
Issues that affect the comprehension of the product.
No action needed or possible. The issue is either fixed, or addressed better by other issues.
Iterations on existing features or infrastructure.
Refactoring existing features that affect the user’s experience of the product.
Issues where further work is prevented by an external dependency.
An issue that will result in new functionality.
Designates that the isssue belongs to the frontend.
Issues that are patched outside the traditional release channel.
No action needed or possible. The issue is deemed out of scope.
Legal implications or requirements for the product.
An issue that addresses small bits of copy on the user interface.
No action needed or possible. The issue is to be addressed at a later date.
Iterations on existing features or infrastructure with a focus on improving speed.
Further information is requested
Refactoring existing features or infrastructure.
Action is being taken, but dependencies need progress.
Issues that affect the user's comprehension of the product.
No action needed or possible. The issue is out of product scope or deemed unnecessary.