project-management | github | gitlab | jira | style-guide

Project management - Organize issues using labels

Here I am listing the labels which I used to organize my tasks in almost all the project management solutions like Jira, Gitlab and GitHub.

Abhith Rajan
Abhith RajanFebruary 06, 2019 · 3 min read · Last Updated:

Labels are a good way to categorize the tasks. But having too many in an unorganized way results more clutter. Here is my way of labeling issues/tasks. This is the way I organize my tasks in GitHub, GitLab and in Jira.

Area

Indicating the area to which issues belong.

LabelDescriptionColor
area/optimizationFine tuning works#8bd9e5
area/security
area/uxUser experience#ccbef7

Priority

Used to prioritize the issues.

LabelDescriptionColor
priority/highRequires immediate attention#d93f0b
priority/mediumRequires attention soon
priority/lowDoes not require immediate attention

Stage

Indicating the current stage of the issue.

LabelDescriptionColor
stage/investigatingSomeone is looking into this
stage/wontfixDoes not regard this as an issue or will not implement this feature
stage/backlogPrioritized to be picked up in current sprint
stage/proposalNo work has been done of this issue
stage/awaiting-responsePotential fix was proposed; awaiting response
stage/pending-releaseWorks associated with this issue is done but not deployed
stage/ready-for-workThe issue is reproducible and in scope
stage/needs-informationNot enough info to reproduce the issue
stage/needs-reviewWork done but needs review
stage/needs-investigatingSomeone needs to look at this
stage/work-in-progressSomeone is working on it#68db1c
stage/in-testDeployed to TEST environment

Stage labels like in progress, backlog etc can be skipped in GitHub if you linked the issue to a project which has relevant columns matching these stages.

Kind

Used to categorize the issues.

LabelDescriptionColor
kind/bug#ee0701
kind/choreWork is required w/ no deliverable to end user
kind/commentComments created via utteranc.es#893aff
kind/documentationImprovements or additions to documentation#5F6D58
kind/duplicateThis issue already exists
kind/featureNew feature that does not currently exist#62fcbe
kind/enhancementRequested enhancement of existing feature#6550ba
kind/question
kind/testing

If you are a colorful person 😉 , suggest me some colors for these labels in the comments 👇

Abhith Rajan

Written byAbhith Rajan
Abhith Rajan is an aspiring software engineer with more than nine years of experience and has a proven successful track record of delivering technology-based products and services.
Connect

Is this page helpful?

This page is open source. Noticed a typo? Or something unclear?
Improve this page on GitHub

Related ArticlesView All

Related VideosView All

Break issues into actionable tasks - GitHub Checkout

How to auto close old support issues using Jira automation

Plan and track projects closer to your code #DemoDays

Related Tools & ServicesView All

toptal.com

gitignore.io

Create useful .gitignore files for your project by selecting from 509 Operating System, IDE, and Programming Language .gitignore templates
github-contributions.now.sh

GitHub Contributions Chart Generator

See all of your GitHub contributions in one image!