Page 3 of 3
Posted: Tue Jul 01, 2008 1:18 pm
by Ryss
The reason we forget about the tracker is that our code rarely, if ever, has bugs. It is always a user related problem.
Yes.
Honestly.
Yeah.
Posted: Tue Jul 01, 2008 1:20 pm
by Naryt
Ryss wrote:The reason we forget about the tracker is that our code rarely, if ever, has bugs. It is always a user related problem.
Yes.
Honestly.
Yeah.
Well, naturally! I mean, if the users would just use it EXACTLY as coded then there would never be any problems!
Posted: Tue Jul 01, 2008 2:14 pm
by Full Bleed
Naryt wrote:One thing I've done in other settings is have a separate development forum devoted just to Bug Reports.
The bug reports then have a specific format:
Problem is that most people won't follow the format. Good idea... hard to enforce.
Posted: Tue Jul 01, 2008 2:20 pm
by Steel Rat
Which is why the bugs should be collected by a third party and displayed.
Ideally the Tracker would have some more specific fields that are required. It's not bad as is, but a bit free-form.
Posted: Tue Jul 01, 2008 2:37 pm
by Phergus
Except that it doesn't address the issue under discussion. A simple way for users to see what bugs or issues may have been introduced in the current build so that they can be aware of the risks in using the latest build.
Doesn't appear that the trackers support build numbers at all.
JIRA looks like a usable bug tracking system but is not something end-users really should be mucking with without a lot of oversight.
The majority of entries are for feature requests and not bugs. There are also a number of entries that have already been resolved as well as a number of duplicates. These things also make it difficult to use for the original purpose.
If the announcement post could be updated with bugs in a fairly timely manner after they are reported (whether by forum post or tracker submission) that would probably benefit the users the most.
Posted: Tue Jul 01, 2008 3:04 pm
by jfrazierjr
Phergus wrote:
Except that it doesn't address the issue under discussion. A simple way for users to see what bugs or issues may have been introduced in the current build so that they can be aware of the risks in using the latest build.
Doesn't appear that the trackers support build numbers at all.
JIRA looks like a usable bug tracking system but is not something end-users really should be mucking with without a lot of oversight.
The majority of entries are for feature requests and not bugs. There are also a number of entries that have already been resolved as well as a number of duplicates. These things also make it difficult to use for the original purpose.
If the announcement post could be updated with bugs in a fairly timely manner after they are reported (whether by forum post or tracker submission) that would probably benefit the users the most.
Agreed. I would not want everyone to just go enter junk into the tracker system. Coming from a support background, you would get 50 copies of the same bug since people rarely actually search for known issues. Better to keep it as clean as possible in my opinion.
Joe