"Bugs can be minor and requirements can be critical"
Exactly, however "Feature requests" are always considered optional and "Bugs" are always pushed through triage. This distinction causes moderately important feature requests to be ignored while moderately important bugs are fixed.
Jeff's point is that the distinction between bugs and feature requests has the unintended consequence of weakening the sorted order of the priorities of this middle range of work items. Additionally, I would argue that identifying something as a either a bug or feature request doesn't provide any value. Spend that energy identifying customer impact.
If it doesn't provide any value and actually requires some effort, stop doing it.
Exactly, however "Feature requests" are always considered optional and "Bugs" are always pushed through triage. This distinction causes moderately important feature requests to be ignored while moderately important bugs are fixed.
Jeff's point is that the distinction between bugs and feature requests has the unintended consequence of weakening the sorted order of the priorities of this middle range of work items. Additionally, I would argue that identifying something as a either a bug or feature request doesn't provide any value. Spend that energy identifying customer impact.
If it doesn't provide any value and actually requires some effort, stop doing it.