Labels

Labels can be applied to issues and merge requests. Group labels are available for any project within the group.

Sponsor 1
Ticket is supported by sponsor 1 (OTF, March 2018 contract)
- Issues
- Merge requests
Sponsor 3
Ticket is supported by Internews (Oct 2018 contract)
- Issues
- Merge requests
Sponsor 2
Ticket is supported by sponsor 2 (ISC, August 2018 contract)
- Issues
- Merge requests
Sponsor 4
Ticket is supported by NLnet (April 2019 grant)
- Issues
- Merge requests
Document
Ticket will produce a document
- Issues
- Merge requests
Security
Ticket has security implications
- Issues
- Merge requests
Battery
Ticket affects battery usage
- Issues
- Merge requests
Infrastructure
Ticket concerns the infrastructure for developing and deploying the project
- Issues
- Merge requests
Liaison
Ticket involves co-ordinating with another organisation
- Issues
- Merge requests
Security audit
Ticket describes an issue identified by an external security audit
- Issues
- Merge requests
Usability
Ticket has usabilty implications
- Issues
- Merge requests
User feedback
Ticket is based on feedback from users or testers
- Issues
- Merge requests
Sponsor 5
Ticket is supported by ISC (January 2020 contract)
- Issues
- Merge requests
Good first issue
Ticket is suitable for a beginning contributor
- Issues
- Merge requests
Sponsor 6
Ticket is supported by sponsor 6 (eQualit.ie, November 2020 contract)
- Issues
- Merge requests
T: bug
Type: bug. Ticket describes a defect that affects the user
- Issues
- Merge requests
T: task
Type: task. Ticket involves work that isn't user-visible, such as refactoring or research
- Issues
- Merge requests
T: feature
Type: feature. Ticket describes a user-visible improvement
- Issues
- Merge requests
P: high
Priority: high. Ticket belongs to the current milestone and should be worked on as soon as possible
- Issues
- Merge requests
P: low
Priority: low. Ticket won’t have the immediate focus of the core team
- Issues
- Merge requests