# Labels research

###### tags: `V3.1 Organization`

## Research

https://www.reddit.com/r/gitlab/comments/fq09mn/labeling_best_practice/


https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63

https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues


https://seantrane.com/posts/logical-colorful-github-labels-18230/

https://blog.adam-marsden.co.uk/better-github-labels-f1360b43e0a7

https://developer.yoast.com/blog/github-labels/

### Image of Gitlab Boards

## Type Labels:

#### Type: Bug
* Bug: crash; App crashes and is unusable
* Bug: Regression; A new version of App broke something

#### Type: Question
#### Type: Idea
* Idea: Marketing
* Idea: Feature
* Idea: UI Design

#### Type: Help needed

---

## Improvement Labels:
#### Improvement: Optimzation
#### Improvement: Enhancement

---

## Problem Labels:
#### problem: Security
#### Problem: Production
#### Problem: Tools
#### Problem: Design
#### Problem: User Interface
#### Problem: Testing

---

## Random Labels
#### Wont Fix
Issues that cant be fixed

#### Ready For Deployment

#### Conflict

#### Code Review

#### CSS
Adding or changing a CSS component

#### JS
Issues related to GitLab's JavaScript components

#### HTML

#### needs weight
This issue requires a weight to be set

#### needs investigation
Relates to issues raised by the community that need further investigation to triage. Please feel free to help investigate!

#### needs scheduling

#### good for new contributors
Issues that are straightforward and can be addressed quickly

#### Unplanned
Urgent requests that were not originally planned for the current milestone

#### cross-group
Denotes the issue belongs to another Group (or even Stage) but is being worked by a different Group's engineering team.

#### Release process
For discussions, processes, and guidelines about GitLab releases.

#### docs-only
Issues and merge requests that only require a documentation change, to differentiate from those coupled with a feature change

#### docs-missing
Issues with missing documentation. Technical Writing team to follow up with Development team.

---
#### Quality
Issues in the domain of the Quality Engineering Department.

#### Quality: performance-test
Quality team testing product performance

#### Quality: test-gap
Test gap analysis for the quality team

#### Quality: test-infrastructure
Quality team testing infrastructure work

#### unit testing
Issues related to unit testing of GitLab code

#### integration testing

---
## Persona Labels

#### Persona: Development Team Lead
Technical Manager, Software Engineering Team Lead, Technical Team Lead, Software Development Director, Development Lead |

#### Persona: Product Designer
UX Designer, Interaction Designer, UI/UX Designer, UI Designer, Experience Designer |

#### Persona: Product Manager
Program Manager, Project Manager, Technical Product Manager, Head of Product |

#### Persona: Release Manager
Product release

#### Persona: Security Analyst
Security Engineer, Security Consultant, or an Application Security Specialist |

#### Persona: Software developer
Software Engineer, Application Developer, Digital Solutions Developer, Consultant, Database Developer, Mobile Developer

#### Persona: Systems Administrator
Systems Engineer, Database Administrator, Infrastructure Engineer, Site Availability Engineer, Site Reliability Engineer |

---