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

Labels

  • backend-weight1
    (Trivial) The problem is very well understood, no extra investigation is required, the exact solution is already known and just needs to be implemented, no surprises are expected, and no coordination with other teams or people is required.
  • backend-weight2
    (Small) The problem is well understood and a solution is outlined, but a little bit of extra investigation will probably still be required to realize the solution.
  • backend-weight3
    (Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.
  • backend-weight4
    (Little more than Medium) Features that are well understood and slightly complex. Bugs that are loosely understood and without a suggested solution.
  • backend-weight5
    (Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.
  • design-weight1
    (Trivial) Mostly small UI changes leading to small incremental UX improvements. No users’ workflow involved in these changes. Requirements are clear and there are no unanswered questions.
  • design-weight2
    (Small) Simple UI or UX change where we understand all of the requirements but may need to find solutions to known questions/problems. These changes should blend in with an actual user workflow.
  • design-weight3
    (Medium) A well-understood change but the scope of work is bigger. Several pages are involved and/or we're starting to design/redesign small flows or connect existing flows between each other. Designers may conduct extensive background research (previous issues, support tickets, review past user research, review analytics, etc). Some unknown questions may arise during the work.
  • design-weight5
    (Large) A complex change where input from group members is needed as early as possible. Spans across multiple pages, and we're working on medium-sized flows that potentially connect with another area of the product. There are significant open questions that need to be answered. The product designer may need to do some research on their own or in collaboration with a researcher, but this isn't always the case. Possible research activities might be to find and/or validate a Job To Be Done, conduct user testing or card-sorting, or do a survey.
  • design-weight8
    (Very large) Complicated changes introducing a new user flow that connects with other large flows and may require input from other designers, product managers, or engineers from the same or another stage group. This is the largest flow design/redesign that we would take on in a single milestone. This requires research where the designer may or may not be working with a researcher to plan and conduct exploratory interviews or user testing sessions
  • docs-weight1
    (Trivial) Tiny change, such as fixing a single misspelling or grammatical mistake.
  • docs-weight2
    (Small) Simple change where problem is well understood, and little or no investigation is required. Typically a few words up to a couple sentences.
  • docs-weight3
    (Medium) Solution is well understood and relatively straightforward, small investigation effort may be required. Typically involving a few sentences.
  • docs-weight5
    (Large) Requires effort in validation through replication or research. Typically, more than a paragraph, less than a page.
  • docs-weight8
    (Very Large) Solution may not be straightforward or known. Significant investigation or expert knowledge required. Typically revising up to a full page, or sections of multiple pages.
  • frontend-weight1
    (Trivial) The problem is very well understood, no extra investigation is required, the exact solution is already known and just needs to be implemented, no surprises are expected, and no coordination with other teams or people is required.
  • frontend-weight2
    (Small) The problem is well understood and a solution is outlined, but a little bit of extra investigation will probably still be required to realize the solution.
  • frontend-weight3
    (Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.
  • frontend-weight4
    (Medium) Features that are well understood and relatively straightforward but still need a good deal of work. Bugs that are relatively poorly understood and may not yet have a suggested solution. Includes some tasks that might be hard to test.
  • frontend-weight5
    (Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.