Corrective action following an incident on GitLab.com

Issues/MRs/Epics related to 13.2 Retrospective

Functionality around health status and how it is managed, displayed, and reported on

For tracking VR advisory (gemnasium/adbcurate) related issues

(optional) PM and Design prioritized design backlog of the next issues to be done

identifies a gap in automation

Generates a 'top' release post item for this issue in the www-gitlab-com project

Generates a 'secondary' release post item for this issue in the www-gitlab-com project

Generates a 'removal' release post item for this issue in the www-gitlab-com project

Generates a 'primary' release post item for this issue in the www-gitlab-com project

Release post item for this issue has been merged

Release post item for this issue is in review

Generates a 'deprecation' release post item for this issue in the www-gitlab-com project

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

(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