Labels

Should be broken down using the Implementation template and sub tasks or may be turned into an epic sub issues. Issues with this label are being ordered to show priorisation. You may also apply a weight.

Work we do for ourselves.

Client is unknown. Do not work on this. Figure out which client this is for!

Issue that are being worked on by part timers

Applied if the engineer should not spend more than 1 workday of time (7h) on this issue.

Applied if the engineer should not spend more than 2 workdays of time (14h) on this issue.

Applied if the engineer should not spend more than 3h on this issue.

MRs related to pipelines(CICD) configuration.

MRs related to improvements of the engineering workflow and release tooling like linters, scripts, etc

Defects in shipped code, not the same as type::technical debt: https://dancrumb.com/engineering/agile/2016/07/08/bugs-are-not-technical-debt.html

A follow-up issue/MR for additional documentation work from merged MRs. This can occur when more work is required after a technical writer review, or if a technical writer review didn’t occur.

user-facing improvements that refine the initial MVC to make it more useful and usable.

Contains work to support the implementation of a feature and/or results in an improvement in the user experience.

Corners that have been cut for speedy devlpmnt - If they cause immediate problems => type::bug !! See: https://dancrumb.com/engineering/agile/2016/07/08/bugs-are-not-technical-debt.html

MRs related to engineering tooling.

Please re-estimate this item due to change of scope or move from past sprint into current sprint.

An issue that won't be fixed e.g. due to deprecation or upcoming replacement.

Applied if at any time during development the issue is blocked. For example: technical issue, open question to PM or PD, cross-group dependency.

Apply to Epics that are Ideas! Requires discussion to decide if it is worth discovering.