5
votes
6answers
346 views

Is it good practice to put bug analysis and fix code in bug report?

When I fix a bug I mention briefly what was the issue and in which revision its fixed. But this way nobody would know how much tricky the issue was and how much effort went in analysis and findings. ...
7
votes
5answers
628 views

should you always enter a bug in a bug tracking system [duplicate]

Possible Duplicate: Should developers enter bugs into the bug tracking system? Should I log trivial fixes? For a project I'll be doing in school soon I will be working with 6 other ...
3
votes
1answer
387 views

How should I organize bugs in redmine?

I'm helping to reogranize several redmine projects; although I have a lot of experience with issue tracking systems, I've never worked with redmine before. What is the best way to organize Issues in ...
3
votes
1answer
291 views

Best practice for marking a bug as resolved in Bugzilla ?

I am wondering what is the best way to handle the situation of marking a bug as resolved and providing a version of component/product in which this fix can be found. Context For a project I am ...
9
votes
7answers
420 views

Should cases be reopened for bugs, or should bugs be opened as a new case?

Currently at my work place we use FogBugz for managing all our features and bugs for our different web applications. When a new feature is to be added to one of our web applications, a new Case is ...
70
votes
16answers
4k views

Should developers enter bugs into the bug tracking system?

While developing (either features or bug fixes) I sometimes happen to discover bugs that are not directly related to what I'm working on. What should I do in that situation. Just fix it? Try to ...
12
votes
3answers
444 views

Using bug-tracking / issue-tracking software to discuss design questions, new tools etc

Does anybody have experience with using a bug-tracking / issue-tracking software like bugzilla, mantis or JIRA not only for bugs or tasks, but to initiate and maintain discussions that in the end lead ...