Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
Low priority development item. Represents a nice to have which we might get too (eventually).
-
Issue which should be moved into development using a normal process.
-
Fix it!!! Highest priority issues which are preventing other work from being done.
-
It's not possible to pursue development of the issue because of problems. Issues that are permanently blocked should be tagged with "Dead."
-
Fixing the issue is hard. The exact causes are unknown, require additional profiling, or a major restructure of the codebase.
-
A permanently blocked issue. It might come back to life, but ... it's not likely.
-
Issues which are currently in a state of planning and preparation, where requirements are being discussed and specifications being written.
-
Duplicate Issue is a duplicate of another issue and adds nothing (or very little) that is new
-
Involves the operations of the technology. Might be related to platform, configuration, or runtime environment.
-
The first time you attempt to do something, you'll get it wrong, so build a prototype first. (Another way of saying we might not know how to do this.)
-
Describe how something should be done so that when you start, you don't make a mess
-
Issues that are queued to be worked on now (but are not currently in development)
-
Issues that will be tackled at some future point (probably in a month)
-
Big picture discussions, clarificiations, and direction. “Where do we want to go?” rather than, “How do we get there?”
Prioritized