Jump to content

Complaint: Bug Tracker Status issues


Guest Schrijver

Recommended Posts

When someone posts a possible bug and Matt or Bfarber looks at the problem, sometimes the status is set to "Bogus", "Cannot reproduce" or "Working as intended".

At this point the original submitter usually tries to clarify the problem with another reply. I see this point happening a lot!

At this point it seems the staff doesn't look at bugs with the above mentioned status anymore. :(

Is the status "Bogus", "Cannot reproduce" or "Working as intended" the same as "Closed" to the staff?

Link to comment
Share on other sites

I was surprised to see the term "Bogus" on some bug topics. That in itself is a fairly inflammatory and if I submitted a bug and got that status I would probably not be pleased.

I think something like "could not be confirmed" would be much more fitting and would not offend the author of the topic. We used that term in the auto industry when someone complained and we could not find the problem.

Imagine what the customer would have said if we wrote BOGUS on the work order. There would have been hell to pay.

Link to comment
Share on other sites

  • Management

That usually means you should do a support ticket as the bug tracker is more of a post-only board not designed for discussion. Often times a bug report ends up being more of a suggestion or request.

We put the item "Bogus" in there because, believe it or not, there are a handful of people who just seem to make things up.

As examples:

http://forums.invisionpower.com/index.php?...14&bug_cat_id=4
http://forums.invisionpower.com/index.php?...57&bug_cat_id=4

Both of these are set to Working as Intended because they are not bug reports but feature requests.

Also: http://forums.invisionpower.com/index.php?...25&bug_cat_id=5

That is set to "bogus" because it's not a bug report but a support issue. Brandon was kind enough to assist him with it in the bug tracker but again that is not really the idea of the bug tracker :) In the end the system is just to post issues.

Link to comment
Share on other sites

I was surprised to see the term "Bogus" on some bug topics. That in itself is a fairly inflammatory and if I submitted a bug and got that status I would probably not be pleased.



I think something like "could not be confirmed" would be much more fitting and would not offend the author of the topic. We used that term in the auto industry when someone complained and we could not find the problem.



Imagine what the customer would have said if we wrote BOGUS on the work order. There would have been hell to pay.



You'll find most software bug trackers use the term "bogus"
Link to comment
Share on other sites

John has a good point

Just because other people do it does not make it right.
Simply saying "not a bug" could suffice.

Up until recently I have been in the retail business for 20 years and was consistently the top producer.

IPB is also in the retail business and in todays politically correct times there is no room to POSSIBLY offend clients. All I am saying is that you can choose to lead or you can follow. Just because other software makers use the term does not necessarily make it something that is conducive to a calm retail environment.

Link to comment
Share on other sites

I understand that some bugs can't be bugs, and I understand that some people get off on posting bugs, but what I don't understand is all the Bogus bugs in the Blogs, including cases where a reply is made by staff fixing the problem, and then its classified as Bogus. And another comment of "It works for me" so it has to be Bogus.

At the very least it would help public perception if a little more tact, and perhaps a little more scrutiny were used with the Bogus classification.

Teejer

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...