Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider migrating to a usable bug tracker. #6052

Closed
vicuna opened this issue Jun 24, 2013 · 6 comments
Closed

Consider migrating to a usable bug tracker. #6052

vicuna opened this issue Jun 24, 2013 · 6 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented Jun 24, 2013

Original bug ID: 6052
Reporter: @dbuenzli
Status: closed (set by @xavierleroy on 2015-12-11T18:19:59Z)
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

I understand the cost and inconvenience for the devs of having to migrate to a new bug tracker.

But the reality for reporters is that this bug tracking system is barely usable. Try e.g. to have the system list your own reports (I'm glad my user name starts with a d and not with a z). Sometimes I'm not even able to find again reports I have made myself without spending 5min interacting with the system.

P.S. free software and self-hosted I don't have anything to recommend, looking for a bug tracker is like looking for a cms, a painful experience. The only usable bugtracker I have used is github's one but I guess that's not an option for the devs.
@vicuna
Copy link
Author

vicuna commented Jun 24, 2013

Comment author: @alainfrisch

Try e.g. to have the system list your own reports

What about:

  • Click on "View Issues".
  • Click on "Reporter".
  • Click on "[Myself]" (second entry in the list).
  • Click on "Apply Filter".

(You can then use "Save Current Filter".)

@vicuna
Copy link
Author

vicuna commented Jun 24, 2013

Comment author: @dbuenzli

Well the fact that I missed that tells something about the system...

@vicuna
Copy link
Author

vicuna commented Jun 24, 2013

Comment author: @yakobowski

Once you're logged, the "Reported by me" subframe is exactly what you're looking for.

(Except for the bugs that were reported on the previous bts. Migrating to a new tool always has hidden costs...)

@vicuna
Copy link
Author

vicuna commented Jun 24, 2013

Comment author: @dbuenzli

In fact the "Reported by me" is very misleading because by default it filter out closed ones. It took me quite some time to realize that.

@vicuna
Copy link
Author

vicuna commented Jun 24, 2013

Comment author: @dbuenzli

It's fun to have a very imperative (modal) bug tracker for a functional programming language. I was caught quite a few times by the stickiness of the filter interface.

@vicuna
Copy link
Author

vicuna commented Jun 25, 2013

Comment author: @xavierleroy

Migrating to a new BTS is a huge cost, because we want to preserve the history from the previous BTS. We did it once and won't do that again any time soon.

Mantis is about as usable (or unusable) as the other major BTSs I've seen. It gets a little time to get used to, just like the others. But it's not because you are personally familiar with X and not with Mantis that we should migrate to X, for any value of X.

@vicuna vicuna closed this as completed Dec 11, 2015
@vicuna vicuna added the bug label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna