“Type” labels. They explain the relationship between current behavior and expected behavior. They bring clarity to users. They are mutually exclusive and comprehensive. Those also help PMs appreciate how much we are focused on depth vs. breadth.

type: bug: It doesn't behave as expected.
type: regression: A bug, but worse, it used to behave as expected.
type: new feature: Expand the scope of the product to solve a new problem.
type: enhancement: It’s an improvement, but we can’t make up our mind whether it's a bug or a new feature.
type: expected behavior: The current behavior is already the one expected.