View Issue Details

IDProjectCategoryView StatusLast Update
0005527GNUnetotherpublic2019-02-21 09:55
ReporterdvnAssigned To 
PrioritylowSeveritytrivialReproducibilityN/A
Status feedbackResolutionreopened 
Product VersionSVN HEAD 
Target VersionFixed in Version 
Summary0005527: Concerns with MantisBT
DescriptionMantis lacks the ability for users to notify other users by calling their name, or easily move around issues. One must go through an elaborate combination of buttons and drop-down menus in order to organize.

I find this counter-productive compared to many of the post-modern issue trackers, such as Github's, Gitlab's, Gog's/Gitea's, JIRA, for example.
TagsNo tags attached.

Activities

Christian Grothoff

2019-01-28 05:58

manager   ~0013491

You're aware that we are running a very old version of Mantis still, right?

dvn

2019-01-28 22:53

developer   ~0013508

I actually was not aware of this, because the copyright at the bottom is updated, I assumed we were running a modern version.

I went ahead and tried out the demo of the latest release running at mantisbt.org, and the layout styling has improved some, but the functionality appears to be very similar to the version we are running.

Christian Grothoff

2019-02-16 15:03

manager   ~0013819

Fixed as Mantis was upgraded. The GitLab CI experiment can proceed independently of this issue, and if that is running by the GNUnet Hacker Meeting we can have an informed discussion about switching...

dvn

2019-02-20 01:32

developer   ~0013890

This is not "fixed", in my opinion. Neither of the issues I bring up are addressed by the update.

1)
> Mantis lacks the ability for users to notify other users by calling their name, or easily move around issues.

This feature has not been added to Mantis.

2)
> One must go through an elaborate combination of buttons and drop-down menus in order to organize.
This has been improved, but for an arbitrary example, selecting the "Category" on a ticket requires scrolling through a (long) drop-down list of categories, as opposed to being able to begin typing the category name and have the list filtered in real time. This type of interface "improvement" is now commonplace in many issue trackers.

schanzen

2019-02-20 08:57

developer   ~0013892

The issue reporting flow is very old school and enterprisey (the irony is that enterprises all make the switch to gitlab which has a more cleaned up interface).
It prompts you with an unnecessary flurry of options when reporting an issue and it is unclear which ones to set and why.
Personally, I am a fan of simplistic issue trackers and opening a Mantis issue always leaves me with a feeling of "did not properly fill it in" or "omg this takes too long".

Christian Grothoff

2019-02-20 09:16

manager   ~0013893

Well, this is the *GNUnet* bugtracker. Sounds to me like you are filing the bug with the wrong project: mantisbt.org has its own bug tracker. I mean, you are not expecting me to stop working on GNUnet and hacking on Mantis now, right? The experimental setup for Gitlab is presumably on the way, so that is also not _this_ bug. So please file bugs here that actually relate to the GNUnet code, and bugs on Mantisbt that relate to the Mantis bug tracker. I am sure the Mantis developers would appreciate qualified feedback.

dvn

2019-02-20 17:40

developer   ~0013907

Last edited: 2019-02-20 17:40

View 2 revisions

My point in filing and commenting on this ticket, and tickets like this, is to document our infrastructure concerns, so that when we make choices, we can point to the "why" we made the choice we did.

Christian Grothoff

2019-02-21 09:55

manager   ~0013919

But your points are wrong:
* Mantis lacks the ability for users to notify other users by calling their name,
  => There is a list of users to "notify" and a field where you can add a name and press "add".
   "calling" makes no sense to me, this is not a voice application. Typing their name into a bug note
  is brittle, if you make a typo, you may think you notified the user but did not. Also it is not clear
  to me that this is desirable.
* or easily move around issues.
  => Not sure how you want to 'move' issues, but there is a 'move' button to move issues to
   other projects, and you can 'edit' the category to move to another category, and you can
   edit the target version to move on the roadmap.

One must go through an elaborate combination of buttons and drop-down menus in order to organize.

  => "elaborate" indeed. All on the bug's edit page, IMO very easy to find.

So the core points the bug report mentions are all not quite right, or a matter of taste. Have you tried bugzilla?

Issue History

Date Modified Username Field Change
2019-01-28 04:41 dvn New Issue
2019-01-28 04:41 dvn Status new => assigned
2019-01-28 04:41 dvn Assigned To => Christian Grothoff
2019-01-28 05:58 Christian Grothoff Note Added: 0013491
2019-01-28 06:00 Christian Grothoff Assigned To Christian Grothoff =>
2019-01-28 06:00 Christian Grothoff Priority high => low
2019-01-28 06:00 Christian Grothoff Severity major => trivial
2019-01-28 06:00 Christian Grothoff Status assigned => acknowledged
2019-01-28 22:53 dvn Note Added: 0013508
2019-02-16 15:03 Christian Grothoff Assigned To => Christian Grothoff
2019-02-16 15:03 Christian Grothoff Status acknowledged => resolved
2019-02-16 15:03 Christian Grothoff Resolution open => fixed
2019-02-16 15:03 Christian Grothoff Fixed in Version => 0.11.0
2019-02-16 15:03 Christian Grothoff Note Added: 0013819
2019-02-16 15:03 Christian Grothoff Product Version => SVN HEAD
2019-02-16 15:03 Christian Grothoff Target Version => 0.11.0
2019-02-20 01:32 dvn Status resolved => feedback
2019-02-20 01:32 dvn Resolution fixed => reopened
2019-02-20 01:32 dvn Note Added: 0013890
2019-02-20 08:57 schanzen Note Added: 0013892
2019-02-20 09:16 Christian Grothoff Status feedback => closed
2019-02-20 09:16 Christian Grothoff Resolution reopened => won't fix
2019-02-20 09:16 Christian Grothoff Note Added: 0013893
2019-02-20 17:40 dvn Status closed => feedback
2019-02-20 17:40 dvn Resolution won't fix => reopened
2019-02-20 17:40 dvn Note Added: 0013907
2019-02-20 17:40 dvn Note Edited: 0013907 View Revisions
2019-02-21 01:41 dvn Assigned To Christian Grothoff =>
2019-02-21 01:43 dvn Fixed in Version 0.11.0 =>
2019-02-21 01:43 dvn Target Version 0.11.0 =>
2019-02-21 01:43 dvn Summary Difficult to keep track of issues => Concerns with MantisBT
2019-02-21 09:55 Christian Grothoff Note Added: 0013919