Too Long; Didn't Read
<em>Compared to all other ticketing </em><a href="https://hackernoon.com/tagged/tools" target="_blank"><em>tools</em></a><em>, </em><a href="https://hackernoon.com/tagged/github" target="_blank"><em>GitHub</em></a><em> Issues is the only platform giving entire freedom to define whatever types of labels you want. All other tools have an opinion on label types, such as priority, severity, component, epic, etc. Now if you consider that the number of GitHub public active repositories amounts now to </em><a href="https://octoverse.github.com/" target="_blank"><em>25 million</em></a><em> at the end of 2017, and that, well, most of these public (understand open-source) projects are managed through GitHub, then you could be wondering if any best practices have emerged. Is there any unique best practices that cannot be applied to other tools? Should we all switch to GitHub to manage our projects there?</em>