Labels can be applied to issues and merge requests. Group labels are available for any project within the group.
Labels
-
Needs::PriorityFamedlyThis label should be set if there is no priority on feature or improvement requests.
-
Needs::RefinementFamedlythe issue is triaged and needs to go to the refinement meeting to be able to set story points to the issue
-
Priority::1-CriticalFamedlyThe Priority 1 label indicates a critically dire issue such as a regression, or failure in existing features. We look at issues with this label frequently. If you find yourself assigning a Prio 1 label to an issue, please be sure that there's a positive handoff between filing and a prospective owner for the issue. Prio 1 issues should be rare. Normally there should be zero open P1 issues. "The world is on fire."
-
Priority::2-MaxFamedlyThe Priority 2 label indicates that the issue deserves immediate attention, such as affecting a top-tier customer. There are generally only one or two Prio 2 bugs at a time, and we aim for there to be none. "A customer is on fire."
-
Priority::3-ImpendingFamedlyA bug with Priority 3 flag indicates that a top-tier customer is about to encounter this bug. Generally, there are less than ten Priority 3 bugs. Issues may not be handled immediately (sometimes some Prio 4 issues are handled first), but are top-of-mind and we explicitly consider them weekly. "A customer is about to be on fire."
-
Priority::4-HighFamedlyThe Priority 4 label indicates high-priority issues that are at the top of the work list. This is the highest priority level an issue can have if it isn't affecting a top-tier customer or breaking the app. Bugs marked Priority 4 are generally actively being worked on unless the assignee is dealing with a P1-P3 bug(or another P4 issue).
-
Priority::5-MediumFamedlyThe Priority 5 label indicates issues that we agree are important to work on, but not at the top of the work list. This is the default level for a bug. An issue at this priority level may not be worked on for a long time. Often an issue at this level will first migrate to Prio 4 before we work on them.
-
Priority::6-LowFamedlyThe Priority 6 label indicates issues we think are valid but not important. This is the default level for new feature requests. We are unlikely to work on such issues unless they form part of a long-term strategic plan (see the Roadmap).
-
Priority::7-NoneFamedlyThe Priority 7 label indicates valid issues that are unlikely to ever be worked on. We use "thumbs-up" on these issues to promote them to Priority 6 or higher based on demand.
-
Progress::BacklogFamedlyThe Refinement of the issue is completed and DoR for the Squad is fulfilled
-
Progress::ReviewFamedlyMerge Request is ready for review. By definition MR review needs to be done by a second developer.
-
Progress::StartedFamedlyThe issue has been picked up for work by a developer in the team and the developer started to work on actively on the issue.
-
Progress::TriageFamedlyThis is the first step of the process. Issue has been recently opened. Product team will identify/evaluate the following: - Clarify questions if required / verify DoR for Product is met. - It’s been identified if Design work is required or not. - Technical Feasibility - Components involved. - Team to work on that issue. - Severity (in case the issue refers to a bug)
Prioritized