Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Issue or Epic that is part of a Working Group's activity stream that is blocked from progressing and requires attention and action to resolve
-
Issue or Epic that is part of a Working Group's activity stream where a decision was made to Cancel the work entailed
-
Issue or Epic that is part of a Working Group's activity stream that has been completed in entirety and no longer requires attention or action
-
Issue or Epic that is part of a Working Group's activity stream that is actively being worked on
-
Issue or Epic that is part of a Working Group's activity stream that has been prioritized, but is not mature enough in definition and scope to be considered ready for work
-
Issue or Epic that is part of a Working Group's activity stream that is appropriately scoped and ready to be worked on
-
New issue, being assessed. | Completion Criteria: Item has enough information to enter problem validation.
-
Clarfying issue scope and prosing solution. | Completion Criteria: Solution defined with sign off from business owners on proposed solution that is valuable, usable, viable and feasible
-
The issue is actively being scoped & refined. | Completion Criteria: Issue includes technical solution, expected outcome, and weight. The technical solution should have enough detail and clarity that any developer (not just the one doing the validation) would be able to pick it up.
-
The issue is fully scoped & refined. | Completion Criteria: A data team member has started to work on the item.
-
Item is in development. | Completion Criteria: Initial engineering work is complete and review process has started.
-
Items are being reviewed by a peer on the data team. | Completion Criteria: MR(s) are merged. Issues had all conversations wrapped up.
-
Items that are blocked or are waiting on feedback or dependencies. Completion Criteria: Work is no longer blocked
Prioritized