Global 'dev' labels
There's a loose convention with prefixing:
sig:*indicates why something is significant to the product/project (
git:*indicates a repo where the relevant code lives (
type:*indicates a general expectation about resourcing (
epic:*indicates that the issue is part of a multifaceted/goal-oriented initiative
needs:*indicates what work is currently blocking (e.g.
steps to replicate, detailed
There are no labels for fine-grained "priorities" because that's too subjective (i.e. all contributors have different priorities), and it's more objective to say why an issue matters (
regression). However, there are prioritization labels for
regression to signal that an issue merits special consideration in the maintenance/release processes.