0 labels
Sort
Sort
-
Organization-level labels that can be used with all repositories under this organization
-
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first. -
Bounty$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue -
Bounty$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue -
Bounty$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue -
Bounty$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue -
Bounty$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue -
Bounty$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue -
Bounty$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue -
Bounty$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue -
Bounty$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue -
Bounty$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue -
MoSCoWCould have
Could have feature in order to satisfy the epic/legendary. -
MoSCoWMust have
Must have feature in order to satisfy the epic/legendary. -
MoSCoWShould have
Should have feature in order to satisfy the epic/legendary. -
Needs feedback
There are questions in the ticket that can not be completed until the project owner provides clarity. -
Points1
1 man-hours worth of work for an expert with no learning curve. -
Points13
13 man-hours worth of work for an expert with no learning curve. -
Points2
2 man-hours worth of work for an expert with no learning curve. -
Points21
21 man-hours worth of work for an expert with no learning curve. -
Points3
3 man-hours worth of work for an expert with no learning curve. -
Points34
34 man-hours worth of work for an expert with no learning curve. -
Points5
5 man-hours worth of work for an expert with no learning curve. -
Points55
55 man-hours worth of work for an expert with no learning curve. -
Points8
8 man-hours worth of work for an expert with no learning curve. -
Points88
88 man-hours worth of work for an expert with no learning curve. -
PriorityBacklog
This ticket has backlogged priority and is not to be worked on yet -
PriorityCritical
The priority is critical -
PriorityHigh
The priority is high -
PriorityLow
The priority is low -
PriorityMedium
The priority is medium -
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed. -
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design. -
StateCompleted
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed. -
StateDuplicate
A ticket that represents the same content as an existing ticket. -
StateIn Progress
A ticket that is actively being developed. -
StateIn Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in. -
StatePaused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay. -
StateUnverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo. -
StateVerified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog. -
StateWont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt. -
TypeBug
Something that doesnt work as intended. -
TypeDiscussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories. -
TypeDocumentation
An error or improvement needed in the documentation. -
TypeEpic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics. -
TypeFeature
Some new functionality not present. -
TypeLegendary
A type of Epic which will contain other Epics. -
TypeSupport
Someone needs help using the project. -
TypeTask
A generic task that doesnt fit into the other type categories. -
TypeTesting
Work exclusively focusing on fixing or expanding testing.