Used to identify issues & MRs that are related to protocol fuzzing

Used to identify issues & MRs that are related to coverage guided fuzzing

Project management surrounding the Fulfillment team

Very large features that usually require the dedication of a FE for the full length of the milestone.

(Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.

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

(Medium) Features that are well understood and relatively straightforward. Bugs that are relatively poorly understood and may not yet have a suggested solution.

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

(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-wide initiatives with a cross-functional impact

Issues for the Frontend team. Covers everything related to the way GitLab behaves (and, to an extent, looks) inside your browser.

Issues which are frequently duplicated, tracked for ease of finding duplicates.

Pajamas Design System: Typography foundation

Pajamas Design System: Spacing foundation

Pajamas Design System: Illustration foundation

Pajamas Design System: Iconography foundation

Pajamas Design System: Design tokens foundation

Pajamas Design System: Color foundation

Pajamas Design System: Animation foundation