Labels

To help people with disabilities & impairments

A large work that can be broken down into a number of smaller stories/issues. Almost always delivered over a set of sprints.

Unusable feature with no workaround / Completely wrong content leading to major misunderstanding by users / Impacts 50%+ users

Broken feature with complex workaround / Wrong content but understandable by User / Impacts between 25%-50% of users / Increase 50%+ efficiency of any core objectives of the app / Very beneificial or Highly requested content / Absence of the feature violates one of the core objectives / Huge user requests (>50)

Broken feature with a easy workaround / Content is not wrong but can be misunderstood / Impacts up to 25% of users / Increase efficiency of any core objectives of the app / Good to have, but alternate contents available already / Help to achieve one or more of the core objectives / Request is not much (5-50)

Inconvenient functionality or cosmetic issue / Small issues like typos / Impacts less than 5% of users / Increase efficiency of any features of the app / Good content, but not much important / Does not go with any core objectives, but may be good to have / Very few requests (<5)

To indicate release plan issues

Open to help and pull requests from approved volunteers

Some aspects of the issue needs to be decided upon by the core team

The implemetation or fix requries a design provided

Require any additional information before proceeding with the issue

The issue requries a bit research before being evaluated. This can be regared as blocked by another Spike issue

Issues that does not add or fix any features but has long term effect of stability and increased maintainability of the project. Subtypes can be add test, refactor

Any kinds of bugs, unexpected features, broken functionalities. Subtypes can be UX, content.

New features or improvements of an existing feature. This includes new content such as translations as well. Subtypes can be UX, improvement, content.