|Anonymous | Login | Signup for a new account||2017-02-24 07:22 CET|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006052||OCaml||-OCaml general||public||2013-06-24 11:15||2015-12-11 19:19|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Status||closed||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0006052: Consider migrating to a usable bug tracker.|
|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.
|Tags||No tags attached.|
> Try e.g. to have the system list your own reports
- 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".)
|Well the fact that I missed that tells something about the system...|
Boris Yakobowski (reporter)
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...)
|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.|
|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.|
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.
|2013-06-24 11:15||dbuenzli||New Issue|
|2013-06-24 11:37||frisch||Note Added: 0009608|
|2013-06-24 12:02||dbuenzli||Note Added: 0009609|
|2013-06-24 13:30||Boris Yakobowski||Note Added: 0009611|
|2013-06-24 13:58||dbuenzli||Note Added: 0009612|
|2013-06-24 14:02||dbuenzli||Note Added: 0009613|
|2013-06-25 12:44||xleroy||Note Added: 0009615|
|2013-06-25 12:44||xleroy||Status||new => resolved|
|2013-06-25 12:44||xleroy||Resolution||open => no change required|
|2015-12-11 19:19||xleroy||Status||resolved => closed|
|2017-02-23 16:36||doligez||Category||OCaml general => -OCaml general|
|Copyright © 2000 - 2011 MantisBT Group|