Project

General

Profile

Bug #206

Need better bug tracking system

Added by none none about 10 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
High
Target version:
Start date:
2010-09-15
Due date:
% Done:

0%

Estimated time:
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 streakIn ProgressSergey Generalov2010-09-07

Actions
Related to site - Feature #442: New Issue should be "available" to unauthenticated usersClosedSergey Generalov2010-12-05

Actions
Related to site - Bug #459: Resolved issues should not be "open". ResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Feature #463: Need non-public bug supportResolvedSergey Generalov2010-12-082010-12-19

Actions
Related to site - Feature #464: Auto-watch supportClosedSergey Generalov2010-12-08

Actions
Related to site - Bug #466: Should be able to build cross-project issue dependenciesResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Bug #108: bugs.i.o should go to illumos issues pageResolvedBryan Horstmann-Allen2010-08-28

Actions
Related to site - Bug #451: Redmine authentication are confused by .illumos.org vs www.ClosedSergey Generalov2010-12-06

Actions
Related to site - Feature #467: Site should list user's loginClosedSergey Generalov2010-12-08

Actions
Related to site - Bug #74: Issue tracker limits possible assigneesRejectedSergey Generalov2010-08-22

Actions
Related to site - Bug #42: Login page tabbing ends up with lost password pageClosedAndre van Eyssen2010-08-10

Actions
Related to site - Bug #77: Move to https completelyResolvedSergey Generalov2010-08-23

Actions
Related to site - Feature #469: Issue tracker needs category supportClosedSergey Generalov2010-12-08

Actions
Related to site - Bug #470: Cannot reopen closed issuesClosedGarrett D'Amore2010-12-08

Actions
Related to site - Feature #471: Make jumping between projects easier for bug trackingResolvedSergey Generalov2010-12-08

Actions
Related to site - Feature #472: Allow issues to span multiple projectsClosedSergey Generalov2010-12-08

Actions
Related to site - Bug #475: Unable to associate other issues while creating new oneResolved2010-12-08

Actions
Related to site - Bug #476: Unhelpful error message when relating a bug to itselfResolvedSergey Generalov2010-12-08

Actions
Related to site - Bug #477: No way to mass-reassign issuesResolvedSergey Generalov2010-12-08

Actions
Related to site - Feature #479: "Related issues" section of an issue should list assignee of related issueRejectedSergey Generalov2010-12-08

Actions
Related to site - Bug #480: Need to be able to change bug/feature/support on an issueResolvedSergey Generalov2010-12-08

Actions
Related to site - Bug #482: Reporters should be able to define bug dataResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Bug #483: Bug workflow a bit offResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Bug #484: Add % done to issue listResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Bug #481: It's hard to tell what's resolved!ResolvedMatt Lewandowsky2010-12-08

Actions
Related to site - Bug #485: Issue permissions are quirkyResolvedGarrett D'Amore2010-12-08

Actions
Related to site - Bug #486: I'm receiving for bugs I've not subscribed toClosedSergey Generalov2010-12-09

Actions
Related to site - Feature #507: Need to identify "good first bugs" and "bite-size" bugsClosedBryan Horstmann-Allen2010-12-12

Actions
Related to site - Bug #746: Redmine shouldn't be publishing email addresses of contributors in the clearClosedSergey Generalov2011-02-21

Actions
#1

Updated by Rich Lowe about 10 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 10 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 10 years ago

  • Assignee set to Sergey Generalov
#4

Updated by Matt Lewandowsky almost 10 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 10 years ago

  • Target version set to 1.0
#6

Updated by Bryan Horstmann-Allen almost 2 years ago

  • Status changed from Feedback to Rejected

Reckon we're sticking with Redmine at this point.

Also available in: Atom PDF