issues and epics related to showing a dependency path to users

Issues about deploy freezes

Issues about per repository and global deploy keys, part of the Release stage of the DevOps lifecycle

Chef recipes/Terraform/Ansible/Rancher/Helm

Issues about deprecation of old features

This issue adds depth to an existing feature.

Relates to the Description template feature introduced in 8.11

Label used to designate issues used as design documentation

(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.

Highly significant changes impacting multiple user flows, a large new feature, and/or a complete redesign. This issue could significantly impact product strategy and would require critical input from others (the wider GitLab community, e-group, customers), and there are many unknowns. This necessitates research where the designer could team up with a researcher and other designers to gather input data, plan and conduct exploratory interviews, lead user testing sessions… It's unlikely we would commit to complete this issue in a milestone, and the preference would be to further clarify requirements and/or break it into smaller issues planned in several milestones.

(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.

(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.

(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.

(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

[Monitor] Design Issues that have been planned but not started

[Monitor] Design Issues that are in the Discovery phase (Fact finding, research, user journeys, story maps)

[Monitor] Design Issues that are in progress (wireframes, mockups, prototypes, etc...)

[Monitor] Design Issues that are ready for engineering (can be closed issues, linked to engineering issues)

[Monitor] Design Issues that are ready for review (Design review && Engineering review)