Labels

• .cs

  .cs

  C Sharp / C#

• .dart

  .dart

  Dart

• .js

  .js

  JavaScript

• .py

  .py

  Python

• .rb

  .rb

  Ruby

• ? Type Question

  ? Type Question

  User/developer question.

• Effort 0

  Effort 0

  Non-work/tracking.

• Effort 0.5

  Effort 0.5

  Simple task (typically non-code).

• Effort 1

  Effort 1

  Simple task (code/non-code).

• Effort 13

  Effort 13

  Placeholder for further splitting. Must never be committed to.

• Effort 2

  Effort 2

  Well-sized task (simple code + tests).

• Effort 21+

  Effort 21+

  Placeholder for further splitting. Must never be committed to.

• Effort 3

  Effort 3

  Task incurring extra overhead (cross-repo work, refactors, complex small features).

• Effort 5

  Effort 5

  Chunky! Ensure this is the smallest that it can be split to before committing to it.

• Effort 8

  Effort 8

  Needs some splitting!

• Impacts All

  Impacts All

  Affects nearly all or all end-users!

• Impacts Few

  Impacts Few

  Does not affect many end-users.

• Impacts Most

  Impacts Most

  Affects a majority of end-users.

• Impacts Some

  Impacts Some

  Affects the average end-user.

• ϟ Type Epic

  ϟ Type Epic

  Describing a big goal. A collection of issues. Should never end up in an iteration.

• ⊖ Blocked ⊖

  ⊖ Blocked ⊖

  Not moving for some reason. Refine prioritization!

• □ Type Story

  □ Type Story

  Feature or requirement written from the user's perspective using non-technical language.

• △ Type Perf

  △ Type Perf

  Performance related.

• ○ Type Bug

  ○ Type Bug

  Regressions/production issues that do not function as intended.

• ✓ Type Task

  ✓ Type Task

  Technical work that is not directly related to a user requirement but still must be completed.

• ⧉ Type Sub-task

  ⧉ Type Sub-task

  Child of another issue. Used to break down stories, tasks, or bugs into individual pieces of work.

• ⧬ Type Spike

  ⧬ Type Spike

  Knowledge exploration for investigating/prototyping a technical approach to some requirement.