Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
  • Research
    Ticket involves the study of sources in order to reach new conclusions
  • Test
    Ticket involves testing a feature and/or reporting the results of a test
  • Tor
    Ticket relates to the Tor Network
  • S: needs more info
    Status: needs more info. Ticket requires more information from the issue reporter
  • 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
  • S: needs diagnosis
    Status: needs diagnosis. Issue reported in ticket requires a technical diagnosis before further triage can be performed
  • S: diagnosed
    Status: diagnosed. Technical diagnosis has been performed on the issue reported in the ticket
  • R: not our bug
    Resolution: not our bug. We are not responsible for the issue reported in the ticket
  • Design
    Ticket involves creating or refining graphical assets
  • Documentation
    Ticket involves creating or refining documentation
  • 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
  • R: fixed
    Resolution: fixed. Issue described by the ticket has been solved
  • R: duplicate
    Resolution: duplicate. Ticket is redundant
  • P: low
    Priority: low. Ticket won’t have the immediate focus of the core team
  • P: high
    Priority: high. Ticket belongs to the current milestone and should be worked on as soon as possible
  • T: feature
    Type: feature. Ticket describes a user-visible improvement
  • T: task
    Type: task. Ticket involves work that isn't user-visible, such as refactoring or research