Labels

• ? Type Question

  User/developer question
• Effort 0

  Non-work/tracking
• Effort 0.5

  Simple task (typically non-code)
• Effort 1

  Simple task (code/non-code)
• Effort 13

  Placeholder for further splitting. Must never be committed to.
• Effort 2

  Well-sized task (simple code + tests)
• Effort 21+

  Placeholder for further splitting. Must never be committed to.
• Effort 3

  Task incurring extra overhead (cross-repo work, refactors, complex small features)
• Effort 5

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

  Needs some splitting!
• Impacts All

  Affects nearly all or all end-users!
• Impacts Few

  Does not affect many end-users.
• Impacts Most

  Affects a majority of end-users.
• Impacts Some

  Affects the average end-user.
• ϟ Type Epic

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

  Not moving for some reason. Refine prioritization!
• □ Type Story

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

  Performance related
• ○ Type Bug

  Regressions/production issues that do not function as intended
• ✓ Type Task

  Technical work that is not directly related to a user requirement but still must be completed.
• ⧉ Type Sub-task

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

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