'Bug' is a too specific term - rename bugs to issues

Bug #928319 reported by Patrick Winchester
34
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
However, not every bug that is filed on launchpad does accurately fit that description. Instead, many bugs fit better into the category of a requested feature, task, missing documentation, and so forth.
Thus, I'd like to propose changing the term "Bug" in Launchpad to something more general and fitting, eg. to the term "Issue".

Revision history for this message
Aaron Bentley (abentley) wrote :
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
rubo77 (rubo77) wrote :

Another solution would be to add a checkbox for "request a feature/Wishlist" and if checked, the term "bug" will change to "feature request" in the interface.

It will still be filed as a "bug" but already with the correct tag.

Revision history for this message
rubo77 (rubo77) wrote :

A user should not feel like *filing a bug* when he is in fact *requesting a feature* or has a wish that is NOT a bug.
The interface should provide a button so you can request a feature instead of filing a bug.

Sure: Internally they will be handled the same, but *on the outside* they should just look different.

So a solution here would be a simple change of the Headline, when someone requests a feature.

see https://bugs.launchpad.net/launchpad/+bug/1321214

summary: - 'Bug' is a too specific term
+ 'Bug' is a too specific term - rename bugs to issues
Revision history for this message
Colin Watson (cjwatson) wrote :

This is very cultural; in some communities the phrase "wishlist bug" is commonplace.

Revision history for this message
`{third: "Beedell", first: "Roke"}`{.JSON5} (rokejulianlockhart) wrote :

Never have I seen such a phrasal, but it doesn't matter anyway. Bug reports and feature requests can be quite easily understood with such separate terminology. Combining the phrasal might cause a user to expect that a component of each must be present in such a filing, which is untrue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.