Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
  • T: epic
    Type: epic. Ticket must be broken down into subtasks
  • Sponsor 6
    Ticket is supported by sponsor 6 (, November 2020 contract)
  • User feedback
    Ticket is based on feedback from users or testers
  • Usability
    Ticket has usabilty implications
  • Security audit
    Ticket describes an issue identified by an external security audit
  • Liaison
    Ticket involves co-ordinating with another organisation
  • Infrastructure
    Ticket concerns the infrastructure for developing and deploying the project
  • P: high
    Priority: high. Ticket belongs to the current milestone and should be worked on as soon as possible
  • Battery
    Ticket affects battery usage
  • Security
    Ticket has security implications
  • UI/UX
    Ticket relates to the user interface and/or user experience
  • T: task
    Type: task. Ticket involves work that isn't user-visible, such as refactoring or research
  • S: stale
    Status: stale. Issue described by the ticket may not be relevant any more, or ticket has had no activity for a long time
  • R: rejected
    Resolution: rejected. Ticket will not be worked on
  • S: in progress
    Status: in progress. Ticket is currently being worked on
  • S: in merge queue
    Status: in merge queue. Ticket is waiting for other branches to be merged before code review
  • S: in code review
    Status: in code review. Ticket is included in an open merge request
  • Good first issue
    Ticket is suitable for a beginning contributor
  • R: fixed
    Resolution: fixed. Issue described by the ticket has been solved
  • T: feature request
    Type: feature request. Ticket describes a user-visible improvement that may or may not be implemented