Bug or Feature? Rethinking the Bug‑vs‑Feature Request Debate

Since I started software development and began using bug‑tracking systems, I’ve repeatedly faced a fundamental question: how can we separate bugs from feature requests?

Of course, a program crash is undeniably a bug, but it may represent only about 10% of daily issues. The real show‑stopper bugs that block releases are quickly fixed, while the majority of entries linger in a gray zone where it’s unclear whether they are bugs or feature requests.

Most bug‑tracking tools force us to choose a side—bug or feature—creating a painful dilemma. From a user’s perspective, there is often no practical difference: if a needed function is missing, the user cannot complete the task, just as an error forces them to stop.

Consider a concrete example: in Windows application development, Visual Studio defaults to the “MS Sans Serif” font instead of the system font. Is this a bug or a feature request?

I argue it is a bug. The issue has existed in Microsoft Connect for over four years, yet it remains classified as a feature request and left unfixed because it does not crash the program or dramatically affect productivity.

Below is a screenshot of the default font in a newly created form (showing the outdated MS Sans Serif) and a comparison with a form that explicitly sets the system GUI font.

The broader issue reflects a general neglect of design among Windows developers, a problem propagated by Visual Studio since 2002.

Design guidelines, such as those from Microsoft’s Windows Vista UX specifications, recommend using the Aero theme and system font (Segoe UI), employing standard controls, and avoiding excessive transparency. The first rule—"applications should use the system font"—directly addresses the problem.

Use Aero theme and system font (Segoe UI)

Use common controls and dialogs

Use standard window borders; use transparency sparingly

… (total of 12 guidelines)

Despite the clear guideline, the Visual Studio bug remains unresolved, likely because it does not affect sales or cause crashes.

Ultimately, the distinction between bug and feature request is often meaningless. Tools like UserVoice deliberately blur the line, leaving users confused and developers able to dismiss work as “not a bug.” The author advocates abandoning the semantic battle and focusing on constructive actions that improve the product.

In summary, the industry should spend less time arguing over terminology and more time delivering tangible improvements based on user feedback.