Bug #206

Need better bug tracking system

Added by none none about 8 years ago. Updated almost 8 years ago.

Status:FeedbackStart date:2010-09-15
Priority:HighDue date:
Assignee:Sergey Generalov% Done:

0%

Category:-
Target version:1.0
Difficulty: Tags:

Description

Many issues are being reported without steps to reproduce and sometimes with just an error message and no further information. The issue tracking system should have a way to enforce other fields.

Suggestion is to use a more mature system like Bugzilla.


Related issues

Related to site - Bug #165: redmine needs to lose its authoritarian streak In Progress 2010-09-07
Related to site - Feature #442: New Issue should be "available" to unauthenticated users Feedback 2010-12-05
Related to site - Bug #459: Resolved issues should not be "open". Resolved 2010-12-08
Related to site - Feature #463: Need non-public bug support In Progress 2010-12-08 2010-12-19
Related to site - Feature #464: Auto-watch support New 2010-12-08
Related to site - Bug #466: Should be able to build cross-project issue dependencies Resolved 2010-12-08
Related to site - Bug #108: bugs.i.o should go to illumos issues page Resolved 2010-08-28
Related to site - Bug #451: Redmine authentication are confused by .illumos.org vs www. Closed 2010-12-06
Related to site - Feature #467: Site should list user's login New 2010-12-08
Related to site - Bug #74: Issue tracker limits possible assignees Rejected 2010-08-22
Related to site - Bug #42: Login page tabbing ends up with lost password page In Progress 2010-08-10
Related to site - Bug #77: Move to https completely Resolved 2010-08-23
Related to site - Feature #469: Issue tracker needs category support Closed 2010-12-08
Related to site - Bug #470: Cannot reopen closed issues Closed 2010-12-08
Related to site - Feature #471: Make jumping between projects easier for bug tracking In Progress 2010-12-08
Related to site - Feature #472: Allow issues to span multiple projects Feedback 2010-12-08
Related to site - Bug #475: Unable to associate other issues while creating new one Feedback 2010-12-08
Related to site - Bug #476: Unhelpful error message when relating a bug to itself New 2010-12-08
Related to site - Bug #477: No way to mass-reassign issues Feedback 2010-12-08
Related to site - Feature #479: "Related issues" section of an issue should list assignee of related issue Feedback 2010-12-08
Related to site - Bug #480: Need to be able to change bug/feature/support on an issue Feedback 2010-12-08
Related to site - Bug #482: Reporters should be able to define bug data Resolved 2010-12-08
Related to site - Bug #483: Bug workflow a bit off Resolved 2010-12-08
Related to site - Bug #484: Add % done to issue list Resolved 2010-12-08
Related to site - Bug #481: It's hard to tell what's resolved! Resolved 2010-12-08
Related to site - Bug #485: Issue permissions are quirky In Progress 2010-12-08
Related to site - Bug #486: I'm receiving for bugs I've not subscribed to Closed 2010-12-09
Related to site - Feature #507: Need to identify "good first bugs" and "bite-size" bugs Closed 2010-12-12
Related to site - Bug #746: Redmine shouldn't be publishing email addresses of contributors in the clear New 2011-02-21

History

#1 Updated by Rich Lowe about 8 years ago

I'm not sure switching systems helps, people always file bugs that are lacking in detail. My experience (though anecdotal) is that if you make more fields mandatory, what you get is not better bugs filed, but less bugs filed. defect.opensolaris.org mandates very little, and bugs.opensolaris.org mandates far too much, but both had their share of great and utterly useless bug reports.

I'm no particular fan of redmine, but this doesn't seem like one of its faults.

#2 Updated by none none about 8 years ago

I don't think OpenSolaris, with its two bug tracking systems, serves as a good reference. Before even reporting a bug, people had to waste time figuring out where to report it. Besides, I always had submit very details bugs to bugs.opensolaris.org (reported against, how to reproduce, details environment info, etc, etc, etc).

Anyway, I just think redmine's is OK for a small project but I think we should plan ahead. Moving from it in the future will probably not be easy and we will end up with a legacy (and two systems, again). Unless we plan to improve it ourselves, but why waste that time when there are other options that have been much more tested?

I do agree that too many mandatory fields actually causes less bugs to be filled. However what we have today is basically just a big text field. The workload is manageable, will it be in the future? Just wanted to point that out, not really emotionally attached to the idea.

#3 Updated by Matt Lewandowsky almost 8 years ago

  • Assignee set to Sergey Generalov

#4 Updated by Matt Lewandowsky almost 8 years ago

  • Status changed from New to Feedback
  • Priority changed from Normal to High

Marking high priority as this is now an umbrella bug and issue tracking is a key component of any large open source project.

#5 Updated by Sergey Generalov almost 8 years ago

  • Target version set to 1.0

Also available in: Atom