From: Максим К. <max...@gm...> - 2015-12-29 20:51:23
|
Hello! I would like to introduce my plugin for mantisbt - Taskodrome - https://github.com/AuthenticEshkinKot/Taskodrome It is an interactive scrum board, which represents tasks as cards and allows user to manage task's assignee and status using drag'n'drop. User with push access to new repo - AuthenticEshkinKot I am new to mantisbt, so I would appreciate any feedback. -- Maxim |
From: Damien R. <dr...@ma...> - 2016-01-02 10:39:20
|
On 2015-12-29 21:51, Максим Кузьмин wrote: > I would like to introduce my plugin for mantisbt - Taskodrome - > https://github.com/AuthenticEshkinKot/Taskodrome Hello Maxim Many thanks for your message. I had a quick look, and your plugin seems very similar to an existing one: https://github.com/mantisbt-plugins/scrum Obviously Taskodrome has nice and useful features in terms of UI which are missing in the Scrum plugin, particularly the drag&drop functionality which is on the todo list [1] as well as the ability to assign issues. I was wondering if you would be interested in contributing to making the existing scrum plugin better, instead of offering a competing one ? Anyway, a few comments on the interface: - if you unassign an issue by dragging it back to 1st column, status remains 'assigned' but without an assignee - what do the blue/red bars at the bottom of the cards mean ? - the Assignment board / Status board selections do not follow the Mantis standard for sub-menus - you're using inline scripts, you should move them to js files (in Mantis 1.3 they will be disabled by CSP); these should be loaded in <head> - CSS is linked before the doctype, should be in <head> - I'm getting 'APPLICATION ERROR #2502 Plugin page not found' trying to access the config page Cheers Damien [1] https://github.com/mantisbt-plugins/scrum/issues/12 |
From: Максим К. <max...@gm...> - 2016-01-02 16:23:36
|
Hello Damien Thanks for your feedback and bugs you've found. There is nothing better for a project on such an early stage of development. Blue/red bars on a bottom of the cards mean issue temperature. If issue was modified recently it will be hotter. If it was not touched it will be colder. Just take a look on issues tomorrow =) I would like to mention that I work with a team and our teamlead is Ivan - iva...@ou... (added in CC). Our team has been using mantis for 4 years and one day we understood that we need a tool for managing tasks in more comfortable way. We knew nothing about Scrum, so we started Taskodrome. I've worked on it for a year and on present moment, the biggest part of Taskodrome's functionality is done. Why don't we contribute to Scrum? The main reason is that it has it's own community with it's own requirements, differs from ours. We've got some plans for Taskodrome and negotiation with Scrum's developers may take too much time. 02.01.2016 13:39, Damien Regad пишет: > On 2015-12-29 21:51, Максим Кузьмин wrote: >> I would like to introduce my plugin for mantisbt - Taskodrome - >> https://github.com/AuthenticEshkinKot/Taskodrome > Hello Maxim > > Many thanks for your message. I had a quick look, and your plugin seems > very similar to an existing one: > > https://github.com/mantisbt-plugins/scrum > > Obviously Taskodrome has nice and useful features in terms of UI which > are missing in the Scrum plugin, particularly the drag&drop > functionality which is on the todo list [1] as well as the ability to > assign issues. > > I was wondering if you would be interested in contributing to making the > existing scrum plugin better, instead of offering a competing one ? > > Anyway, a few comments on the interface: > > - if you unassign an issue by dragging it back to 1st column, status > remains 'assigned' but without an assignee > - what do the blue/red bars at the bottom of the cards mean ? > - the Assignment board / Status board selections do not follow the > Mantis standard for sub-menus > - you're using inline scripts, you should move them to js files (in > Mantis 1.3 they will be disabled by CSP); these should be loaded in <head> > - CSS is linked before the doctype, should be in <head> > - I'm getting 'APPLICATION ERROR #2502 Plugin page not found' trying to > access the config page > > Cheers > Damien > > [1] https://github.com/mantisbt-plugins/scrum/issues/12 > > > > ------------------------------------------------------------------------------ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev -- Maxim |
From: Damien R. <dr...@ma...> - 2016-01-03 00:13:55
|
On 2016-01-02 17:23, Максим Кузьмин wrote: > Why don't we contribute to Scrum? The main reason is that it has it's > own community with it's own requirements, differs from ours. We've got > some plans for Taskodrome and negotiation with Scrum's developers may > take too much time. For the record, Scrum's original author is no longer maintaining the plugin, so it's essentially a community project now; I've been doing a few random updates to it, but it's very low priority for me, and there is no roadmap or anything. This means the project could probably go in the direction you want it to, without much in terms of negotiation, so you shouldn't be concerned about time/effort in this area. In fact, you could even take things over if you're interested Anyway, it's your call. I just thought it would made sense to join efforts and have a single Scrum plugin that does it all rather than 2 competing products. |
From: Victor B. <vb...@gm...> - 2016-01-03 02:39:41
|
It would be useful to add some animated gifs / images to the readme of the plugin. I would also add some more details about scenarios and supported features. It is generally useful to give users an idea of what the plugin achieves before going through the trouble of installing it and testing it. Here is an example: https://github.com/mantisbt-plugins/EventLog <https://github.com/mantisbt-plugins/EventLog> > On Jan 2, 2016, at 4:13 PM, Damien Regad <dr...@ma...> wrote: > > On 2016-01-02 17:23, Максим Кузьмин wrote: >> Why don't we contribute to Scrum? The main reason is that it has it's >> own community with it's own requirements, differs from ours. We've got >> some plans for Taskodrome and negotiation with Scrum's developers may >> take too much time. > > For the record, Scrum's original author is no longer maintaining the > plugin, so it's essentially a community project now; I've been doing a > few random updates to it, but it's very low priority for me, and there > is no roadmap or anything. > > This means the project could probably go in the direction you want it > to, without much in terms of negotiation, so you shouldn't be concerned > about time/effort in this area. In fact, you could even take things over > if you're interested > > Anyway, it's your call. I just thought it would made sense to join > efforts and have a single Scrum plugin that does it all rather than 2 > competing products. > > > > ------------------------------------------------------------------------------ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Максим К. <max...@gm...> - 2016-01-10 13:43:45
|
Hello Damien I've got some updates on your comment list: 1. - if you unassign an issue by dragging it back to 1st column, status remains 'assigned' but without an assignee As far as I can see, this is default mantis behavior. If you unassign an issue using default interface, issue will save its status. 2. - what do the blue/red bars at the bottom of the cards mean ? As I mentioned earlier, this is "temperature". 3. - the Assignment board / Status board selections do not follow the Mantis standard for sub-menus To be fixed. 4. - you're using inline scripts, you should move them to js files (in Mantis 1.3 they will be disabled by CSP); these should be loaded in <head> Fixed 5. - CSS is linked before the doctype, should be in <head> Correct me if I'm wrong, but it's already in <head>. 6. - I'm getting 'APPLICATION ERROR #2502 Plugin page not found' trying to access the config page Fixed - empty configuration page was added. 02.01.2016 13:39, Damien Regad пишет: > On 2015-12-29 21:51, Максим Кузьмин wrote: >> I would like to introduce my plugin for mantisbt - Taskodrome - >> https://github.com/AuthenticEshkinKot/Taskodrome > Hello Maxim > > Many thanks for your message. I had a quick look, and your plugin seems > very similar to an existing one: > > https://github.com/mantisbt-plugins/scrum > > Obviously Taskodrome has nice and useful features in terms of UI which > are missing in the Scrum plugin, particularly the drag&drop > functionality which is on the todo list [1] as well as the ability to > assign issues. > > I was wondering if you would be interested in contributing to making the > existing scrum plugin better, instead of offering a competing one ? > > Anyway, a few comments on the interface: > > - if you unassign an issue by dragging it back to 1st column, status > remains 'assigned' but without an assignee > - what do the blue/red bars at the bottom of the cards mean ? > - the Assignment board / Status board selections do not follow the > Mantis standard for sub-menus > - you're using inline scripts, you should move them to js files (in > Mantis 1.3 they will be disabled by CSP); these should be loaded in <head> > - CSS is linked before the doctype, should be in <head> > - I'm getting 'APPLICATION ERROR #2502 Plugin page not found' trying to > access the config page > > Cheers > Damien > > [1] https://github.com/mantisbt-plugins/scrum/issues/12 > > > > ------------------------------------------------------------------------------ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev -- Maxim |
From: Damien R. <dr...@ma...> - 2016-01-10 14:50:04
|
On 2016-01-10 14:43, Максим Кузьмин wrote: > 1. > > - if you unassign an issue by dragging it back to 1st column, status > remains 'assigned' but without an assignee > > As far as I can see, this is default mantis behavior. If you > unassign an issue using default interface, issue will save its status. You're right. I vaguely recall an open issue on the tracker to address that. > 5. > > - CSS is linked before the doctype, should be in <head> > > Correct me if I'm wrong, but it's already in <head>. I don't remember TBH, and no time to test now, but I recall viewing source and seeing the CSS link as the very first line in the HTML generated page. D |