Organising Github Issues Effectively

At work, we use github issues as the source of truth for any new bugs that are found. We push any issues directly into github, and this works quite well.

The problem with our approach, however, is that without proper tagging, issues get lost, lose their clarity, and it often takes a decent time investment from a developer to even get enough context around the issue to re-create it and solve it.

Looking to improve this process, I started investigating what other companies do, and found this simple yet extremely useful article:

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

Robin uses a set of pre-defined tags that are used across all of their repositories. I am starting to integrate their concepts of tagging categories with clear colour codes into our main repo and it’s working great. Hopefully this article helps you as much as it did me.

What do you think of this method? I would love to hear your thoughts.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.