Skip to content

Labels

Labels

  • Use this label for issues requiring deeper investigation, research, or planning.
  • For issues or tasks specifically involving server-side logic, APIs, databases, or infrastructure.
  • This issue is blocked by another issue or an external factor.
  • Something isn’t working as intended and needs fixing.
  • Issues that should create or update developer-focused documentation.
  • Covers UI/UX tasks, styling, or any client-side work.
  • A triage label for new issues or tasks that haven’t been categorized or prioritized yet.
  • Issues that cannot yet be committed to the backlog; they require further vetting/future scheduling.
  • Marks user stories from an accountant’s perspective.
  • Marks user stories from a client’s perspective.
  • Team workflow/process improvements (e.g., revise code review process)
  • Proposals or issues affecting end-user functionality or product direction
  • Issues needing an initial review or scoping by the creator/importer before further labeling.
  • An issue with no parent or that may be an umbrella issue, epic, ...
  • Areas needing technical improvements (performance, architecture, testing, tech debt, etc.)
  • Inspired by tickler files, review one-time or recurring items on a set date.
  • Issues that should create or update user-facing documentation or help content.