Priorities and labels reference

Priorities and labels are the two controls that keep a busy board readable. A priority ranks how urgent a bug is, and labels group bugs by anything else that matters to your team: the feature, the platform, or the kind of failure. This reference explains what each one means and how to use them together.

Priority answers one question: how soon does this need attention? BugMojo uses five fixed levels so a priority means the same thing on every board.

• Critical: the app is down, blocking many users, or data is at risk. Drop everything.
• High: a major feature is broken with no easy workaround. Fix in the current cycle.
• Medium: a real problem, but there is a workaround. The default weight for most bugs.
• Low: minor or cosmetic. Fix when it is convenient.
• None: no priority set yet. Treat these as an inbox that still needs triage.

Labels are free-form tags you create and attach to bugs. Unlike priority and status, they are not fixed: you define whatever categories fit your team, such as checkout, regression, mobile, or needs-repro. A bug can carry as many labels as it needs, and every label is available across the boards in a project so tagging stays consistent.

Add or remove labels from the Labels field on the bug detail page. Because labels are just tags, they pair naturally with filters: narrow a board to one label, combine a label with a priority or assignee, and save that combination as a view your team returns to.