Hi,
is it just my impression that Mantis was more feature rich an had better layout? An example: Mantis has "Reported by me".
(I understand that new tracker is better wired with version system which is benefit for developers.)
Thanks, V.
Mailing lists / lazarus / 2021-08
Mantis vs GitLab issue tracker
11 messages · 7 people · –
- MMichael Van Canneyt 3
- LLacaK 2
- MMartin Frb 2
- BBart 1
- FFlorian Klämpfl 1
- MMarc Weustink 1
- +1 more
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
PM Vojtěch Čihák wroteis it just my impression that Mantis was more feature rich an had better layout?
Agreed.
However, maintaining Mantis (and our svn server) had become a nightmare. Unfortunately the issue tracker of GitLab doesn't offer the functionality we were used to.
But, that ship has sailed.
It is what it is...
is it just my impression that Mantis was more feature rich an had better layout? An…
Vojtěch Čihák wrote 7 lines
Yes, indeed. Though some of it is what you are used to...
About monitoring, you can add "reactions" (emoticons /visible to others, but so was monitoring).
Then you can search "my reaction"
About issues you monitored in Mantis:
https://forum.lazarus.freepascal.org/index.php/topic,55750.msg415076.html#msg415076
What is new in Gitlab...
* You can mention people, which afaik creates an entry in their todo.
* You can (un)subscribe per issue, to get mails
* As you said, better integration with the repro. Online links between commits and issues.
On Fri, Aug 13, 2021 at 9:02 PM Vojtěch Čihák via lazarus Agreed. However, maintaining…
Show quoted text 12 lines
This is my experience with all „modern“ software, often it’s functionality is reduced. But as Bart said, keeping Mantis up-to-date was a nightmare task as we used customized source code, I think because of strange notification behaviour.
"Florian Klämpfl wrote 16 lines
Another problem was the internal notification processing of mantis when you have a "lot" of members.
Instead of using database queries (something which is the key feature of a db) to select the addresses to send mail to, it loaded all members as php object in memory and filters out all addresses based on user preference. This is time consuming, and has a severe impact on memory usage of the server.
Marc
is it just my impression that Mantis was more feature rich an had better layout? An…
is it just my impression that Mantis was more feature rich an had better layout? An example: Mantis has "Reported by me".
It is my impression too.
I would like to see panels (like in
https://gitlab.com/groups/freepascal.org/-/boards):
- Reported by me (filter Author="my account")
- Assigned to me (filter Asignee="my account")
- Unassigned (filter Asignee=None)
- (Resolved); here is sufficient for me list of recently changed issues as is there already
In other words : is there way how to add custom boards based on above filters?
L.
LacaK wrote 5 lines
You can find this in your 'issues' list?
Show quoted text 10 lines
I can create new boards, but not with the filters you want. There is no 'active user' filter. (i.e. "me" or so)
I can create lists filtered on label, assignee or milestone.
I could create a label 'unassigned' to filter on. but then we would need to apply that to all new issues. This can be automated. Then I could use it to add an 'unassigned' list. The label would need to be removed when a user is assigned to an issue. This can probably also be automated.
They are working on a named filter system. When that exists, more things will be possible:
https://gitlab.com/gitlab-org/gitlab/-/issues/14512
Michael.
Michael Van Canneyt wrote 6 lines
See my last mail.
See "My reactions"
Show quoted text 15 lines
Ideally each boards has only filters by the same kind.
Because if you have a board, with lists:
- label = x
- milestone = y
Then you can drag and drop issues between the boards. But drag and drop means to remove/add the label/milestone.
So the current board, with diff milestones is ok. because you can mave issues from one milsestone to another
Martin Frb wrote 38 lines
I've been looking at https://github.com/jdalrymple/gitbeaker
Using pas2js it should be relatively easy to make a small webpage that recreates the mantis view. All it would need is a token or oauth key.
Such a page can be hosted on the FPC webserver. The browser would do all other requests directly to gitlab, so this puts no load on the FPC webserver except of the initial page request.
Michael.
You can find this in your 'issues' list? I can create new boards, but not with the…
Show quoted text 25 lines
Ok I understand.
If there is no straight forward, simple way then IMO no need to complicate things.
I am here as pure user and I am asking for simple solutions ;-) I only shared impression that GitLab issue tracker is for me also less intuitive and practical compared to Mantis.
(of course I accept others developers arguments related to maintenance cost of GitLab versus Mantis and so on ...)
L.
LacaK wrote 26 lines
It's a different system, with different possibilities. I find the filter system very easy to use compared to Mantis, so I won't miss the old one.
One can lament the demise of the old system, but in time I suspect most will adapt to the new one.
As said, I'm looking at creating a frontpage for a mantis-like overview. With pas2js it should be easy to do.
Michael.
