mantisbt-dev — MantisBT development discussions

[mantisbt-dev] Howto add contributors to github repo ?

[Louis B. <lba...@gm...>]

Hi,
I would like to add some contributors to the CodevTT github
repository, hosted on mantisbt-plugins.
How can I do that ? (the 'Settings' icon is not displayed).

Contributors: Nikerabbit and siebrand (people from translatewiki.net)

https://github.com/mantisbt-plugins/codev

Best regards

Louis BAYLE
http://CodevTT;org

Re: [mantisbt-dev] v1.3 changelog ?

[Damien R. <dr...@ma...>]

On 2016-01-31 01:30, Louis BAYLE wrote:
> thank you for your quick answer. I checked the schema.php file of
> course, it defines the DB structure changes, but there's nothing about
> encoding changes of existing values.

Please note that we also have 'UpdateFunction' upgrade steps, which call 
specific PHP code which are defined in install_helper_functions_api.php. 
In this specific case, look at

https://github.com/mantisbt/mantisbt/blob/master/admin/schema.php#L827

and also

https://github.com/mantisbt/mantisbt/blob/master/core/install_helper_functions_api.php#L634
https://github.com/mantisbt/mantisbt/blob/master/core/install_helper_functions_api.php#L666

Hope this helps.

Re: [mantisbt-dev] v1.3 changelog ?

[Louis B. <lba...@gm...>]

Hi Victor,
thank you for your quick answer. I checked the schema.php file of
course, it defines the DB structure changes, but there's nothing about
encoding changes of existing values.

are there other tables where this kind of changes have been done ?

best regards
Louis
Louis BAYLE
Tel: +33 (0)4.42.604.734
lba...@gm...


On Sun, Jan 31, 2016 at 1:17 AM, Victor Boctor <vb...@gm...> wrote:
> Your best option is to inspect the schema.php file which is the
> authoritative source for such information.
>
> On January 30, 2016 at 4:15:24 PM, Louis BAYLE (lba...@gm...)
> wrote:
>
> Hi,
> I realy need to know if there is some documentation about the DB
> changes made in mantis 1.3. the blog does not contain the technical
> changes I am looking for:
>
> I just discovered that you changed the encoding of some variables in
> the database (serialize => json_encode) and realy, it is so much time
> consuming tracking all that changes, I hit my head against the walls
> to make CodevTT compatible with v1.3.
>
> CodevTT is not a mantis plugin, so I can't use the mantis API and I
> make direct access to the database.
>
> please please, is there any documentation about all the DB changes ?
>
> Louis
>
>
>
>
> On Fri, Nov 13, 2015 at 5:51 PM, Roland Becker <ro...@at...> wrote:
>> Start reading
>> https://www.mantisbt.org/blog/?p=416
>> https://www.mantisbt.org/blog/?p=425
>>
>> Roland
>>
>>> Louis BAYLE <lba...@gm...> hat am 13. November 2015 um 17:45
>>> geschrieben:
>>>
>>>
>>> Hi,
>>> I don't know when you plan to release v1.3 but I would like the
>>> CodevTT plugin to be ready when it comes out.
>>>
>>> So far, i noticed that the configuration files have moved to another
>>> directory, and when upgrading from 1.2 to 1.3beta the installer
>>> updated the DB.
>>> So there are some changes that I need to be aware of.
>>>
>>> Is there a changelog from 1.2 to 1.3 available (architecture & features)
>>> ?
>>>
>>> Thank you very much,
>>> best regards,
>>>
>>> Louis BAYLE
>>> http://codevtt.org
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> mantisbt-dev mailing list
>>> man...@li...
>>> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

Re: [mantisbt-dev] v1.3 changelog ?

[Victor B. <vb...@gm...>]

Your best option is to inspect the schema.php file which is the authoritative source for such information.

On January 30, 2016 at 4:15:24 PM, Louis BAYLE (lba...@gm...) wrote:

Hi, 
I realy need to know if there is some documentation about the DB 
changes made in mantis 1.3. the blog does not contain the technical 
changes I am looking for: 

I just discovered that you changed the encoding of some variables in 
the database (serialize => json_encode) and realy, it is so much time 
consuming tracking all that changes, I hit my head against the walls 
to make CodevTT compatible with v1.3. 

CodevTT is not a mantis plugin, so I can't use the mantis API and I 
make direct access to the database. 

please please, is there any documentation about all the DB changes ? 

Louis 




On Fri, Nov 13, 2015 at 5:51 PM, Roland Becker <ro...@at...> wrote: 
> Start reading 
> https://www.mantisbt.org/blog/?p=416 
> https://www.mantisbt.org/blog/?p=425 
> 
> Roland 
> 
>> Louis BAYLE <lba...@gm...> hat am 13. November 2015 um 17:45 
>> geschrieben: 
>> 
>> 
>> Hi, 
>> I don't know when you plan to release v1.3 but I would like the 
>> CodevTT plugin to be ready when it comes out. 
>> 
>> So far, i noticed that the configuration files have moved to another 
>> directory, and when upgrading from 1.2 to 1.3beta the installer 
>> updated the DB. 
>> So there are some changes that I need to be aware of. 
>> 
>> Is there a changelog from 1.2 to 1.3 available (architecture & features) ? 
>> 
>> Thank you very much, 
>> best regards, 
>> 
>> Louis BAYLE 
>> http://codevtt.org 
>> 
>> ------------------------------------------------------------------------------ 
>> _______________________________________________ 
>> mantisbt-dev mailing list 
>> man...@li... 
>> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev 

------------------------------------------------------------------------------ 
Site24x7 APM Insight: Get Deep Visibility into Application Performance 
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month 
Monitor end-to-end web transactions and take corrective actions now 
Troubleshoot faster and improve end-user experience. Signup Now! 
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 
_______________________________________________ 
mantisbt-dev mailing list 
man...@li... 
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev 

Re: [mantisbt-dev] v1.3 changelog ?

[Louis B. <lba...@gm...>]

Hi,
I realy need to know if there is some documentation about the DB
changes made in mantis 1.3. the blog does not contain the technical
changes I am looking for:

I just discovered that you changed the encoding of some variables in
the database (serialize => json_encode) and realy, it is so much time
consuming tracking all that changes, I hit my head against the walls
to make CodevTT compatible with v1.3.

CodevTT is not a mantis plugin, so I can't use the mantis API and I
make direct access to the database.

please please, is there any documentation about all the DB changes ?

Louis




On Fri, Nov 13, 2015 at 5:51 PM, Roland Becker <ro...@at...> wrote:
> Start reading
> https://www.mantisbt.org/blog/?p=416
> https://www.mantisbt.org/blog/?p=425
>
> Roland
>
>> Louis BAYLE <lba...@gm...> hat am 13. November 2015 um 17:45
>> geschrieben:
>>
>>
>> Hi,
>> I don't know when you plan to release v1.3 but I would like the
>> CodevTT plugin to be ready when it comes out.
>>
>> So far, i noticed that the configuration files have moved to another
>> directory, and when upgrading from 1.2 to 1.3beta the installer
>> updated the DB.
>> So there are some changes that I need to be aware of.
>>
>> Is there a changelog from 1.2 to 1.3 available (architecture & features) ?
>>
>> Thank you very much,
>> best regards,
>>
>> Louis BAYLE
>> http://codevtt.org
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> mantisbt-dev mailing list
>> man...@li...
>> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

Re: [mantisbt-dev] v1.3.x deprecated helper_alternate_class() ?

[Damien R. <dr...@ma...>]

Louis BAYLE <lbayle.work@...> writes:
> Ok, thank you Damien.
> So I'll have to maintain two versions of the plugin

Either that, or as other plugin maintainers have decided to do, use
conditions to dynamically generate HTML adapted to currently running
MantisBT core. But maybe it's not practical considering the size of CodevTT.
Anyway it's up to you.

> shadok)

Tiens, voilà une référence qui ne me rajeunit pas :-/

D

Re: [mantisbt-dev] v1.3.x deprecated helper_alternate_class() ?

[Louis B. <lba...@gm...>]

Ok, thank you Damien.
So I'll have to maintain two versions of the plugin. As we say in
France: "If there is no solution, then there's no problem..." (devise
shadok)

:-)

Best regards
Louis BAYLE
Tel: +33 (0)4.42.604.734
lba...@gm...


On Thu, Jan 21, 2016 at 1:12 PM, Damien Regad <dr...@ma...> wrote:
> Hi Louis,
>
> Louis BAYLE <lbayle.work@...> writes:
>> I guess the fix is to simply remove the use of
>> helper_alternate_class() with no replacement at all,
>
> This is correct, and works as long as the parent container has a class which
> handles the alternating row colors, e.g. 'table-container' or 'form-container'.
>
>> this works on 1.3 but on 1.2.x the list widget that I added is no more
>> displayed. Does this mean there is no possibility to have
>> compatibility for 1.3 and 1.2 ?
>
> Again, correct. This change is not backwards compatible. In 1.3 we also
> reduce usage of html tables for layout, and use more divs, so in many cases
> the page layout is very different.
>
> To maintain backwards compatibility with 1.2 in parallel with 1.3 support,
> you need to customize your code to take into consideration the MantisBT version.
>
> I personnally prefer to maintain 2 distinct branches.
>
> Hope this helps.
>
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

Re: [mantisbt-dev] v1.3.x deprecated helper_alternate_class() ?

[Damien R. <dr...@ma...>]

Hi Louis,

Louis BAYLE <lbayle.work@...> writes:
> I guess the fix is to simply remove the use of
> helper_alternate_class() with no replacement at all,

This is correct, and works as long as the parent container has a class which
handles the alternating row colors, e.g. 'table-container' or 'form-container'.

> this works on 1.3 but on 1.2.x the list widget that I added is no more
> displayed. Does this mean there is no possibility to have
> compatibility for 1.3 and 1.2 ?

Again, correct. This change is not backwards compatible. In 1.3 we also
reduce usage of html tables for layout, and use more divs, so in many cases
the page layout is very different.

To maintain backwards compatibility with 1.2 in parallel with 1.3 support,
you need to customize your code to take into consideration the MantisBT version.

I personnally prefer to maintain 2 distinct branches.

Hope this helps.

Re: [mantisbt-dev] v1.3.x deprecated helper_alternate_class() ?

[Louis B. <lba...@gm...>]

Hi again,
I found this commit in the mantisbt git repository: SHA1 = 6aa5e9b81fb2f

I guess the fix is to simply remove the use of
helper_alternate_class() with no replacement at all,

this works on 1.3 but on 1.2.x the list widget that I added is no more
displayed. Does this mean there is no possibility to have
compatibility for 1.3 and 1.2 ?

best regards
Louis


Louis BAYLE
Tel: +33 (0)4.42.604.734
lba...@gm...


On Wed, Jan 20, 2016 at 5:52 PM, Louis BAYLE <lba...@gm...> wrote:
> Hi,
> I have a deprecation error on helper_alternate_class() on the CodevTT plugin.
>
> There are several discussions on the subject (Mantis #0017437), but it
> is not clear to me on what CSS fix I should apply.
> Could you please tell me where I can find find some doc about it ?
>
> here is my code:
> https://github.com/lbayle/codev/blob/master/mantis_plugin/CodevTT/CodevTT.php#L289
>
> Thank you very much,
>
> looking forward 1.3 to come out !
>
>
> Louis BAYLE
> lba...@gm...
> http://CodevTT.org

[mantisbt-dev] v1.3.x deprecated helper_alternate_class() ?

[Louis B. <lba...@gm...>]

Hi,
I have a deprecation error on helper_alternate_class() on the CodevTT plugin.

There are several discussions on the subject (Mantis #0017437), but it
is not clear to me on what CSS fix I should apply.
Could you please tell me where I can find find some doc about it ?

here is my code:
https://github.com/lbayle/codev/blob/master/mantis_plugin/CodevTT/CodevTT.php#L289

Thank you very much,

looking forward 1.3 to come out !


Louis BAYLE
lba...@gm...
http://CodevTT.org

Re: [mantisbt-dev] New mantisbt plugin

[Damien R. <dr...@ma...>]

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

Re: [mantisbt-dev] New mantisbt plugin

[Максим К. <max...@gm...>]

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

Re: [mantisbt-dev] New plugin

[Alleen W. <wc...@gm...>]

Hi Damien,

I have already to change the ownership to mantisbt-plugins.

Thanks!!!

BR.

Alleen Wang

2016-01-02 21:24 GMT+08:00 Damien Regad <dr...@ma...>:

> On 2015-08-03 06:25, Alleen Wang wrote:
> > I creaed a plugin for mantisBT.
> >
> > Name : GoogleOauth.
> > Description : Add google oauth function into mantisBT.
> > GitHub link : https://github.com/alleen/GoogleOauth
> >
> > I would like to add a plugin to your organization
> > (https://github.com/mantisbt-plugins).
>
> Greetings
>
> Thanks for the plugin, and apologies for the late reply. I created a
> group to host the plugin in the mantisbt-plugins org, and sent you an
> invite.
>
> I let you transfer ownership or fork as you prefer, let me know if you
> need help.
>
> Damien
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>



-- 
Alleen Wang

Re: [mantisbt-dev] Proposal for a new plugin "EasyEnter"

[Frithjof G. <fg...@pr...>]

On 2016-01-02 14:06 Damien Regad wrote:
> On 2015-09-01 18:10, Frithjof Gnas wrote:
>> Hello everyone,
>>
>> some weeks ago I wrote a simple Mantis-plugin which may be useful for some other
>> people as well.
>>
>> Link to repository:
>> https://github.com/fg-ok/EasyEnter
> 
> Dear Frithjof
> 
> I created a new team in mantisbt-plugins for your plugin, and sent you 
> an invitation.
> 
> This is the first time I do this since Github changed the way they 
> handle access rights in orgs, so I'm not 100% sure about what privileges 
> you'll get once you accept the invitation; if you're not able to 
> transfer ownership of your plugin after you join, let me know and I'll 
> try to fix it.

Dear Damien,

thanks a lot. It worked well (it was my first time transferring anything
on Github ever ;-)).


Greetings
Frithjof

Re: [mantisbt-dev] New mantisbt plugin

[Victor B. <vb...@gm...>]

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

Re: [mantisbt-dev] New mantisbt plugin

[Damien R. <dr...@ma...>]

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.

Re: [mantisbt-dev] New mantisbt plugin

[Максим К. <max...@gm...>]

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

Re: [mantisbt-dev] New plugin

[Damien R. <dr...@ma...>]

On 2015-08-03 06:25, Alleen Wang wrote:
> I creaed a plugin for mantisBT.
>
> Name : GoogleOauth.
> Description : Add google oauth function into mantisBT.
> GitHub link : https://github.com/alleen/GoogleOauth
>
> I would like to add a plugin to your organization
> (https://github.com/mantisbt-plugins).

Greetings

Thanks for the plugin, and apologies for the late reply. I created a 
group to host the plugin in the mantisbt-plugins org, and sent you an 
invite.

I let you transfer ownership or fork as you prefer, let me know if you 
need help.

Damien

Re: [mantisbt-dev] Proposal for a new plugin "EasyEnter"

[Damien R. <dr...@ma...>]

On 2015-09-01 18:10, Frithjof Gnas wrote:
> Hello everyone,
>
> some weeks ago I wrote a simple Mantis-plugin which may be useful for some other
> people as well.
>
> Link to repository:
> https://github.com/fg-ok/EasyEnter

Dear Frithjof

I created a new team in mantisbt-plugins for your plugin, and sent you 
an invitation.

This is the first time I do this since Github changed the way they 
handle access rights in orgs, so I'm not 100% sure about what privileges 
you'll get once you accept the invitation; if you're not able to 
transfer ownership of your plugin after you join, let me know and I'll 
try to fix it.

Damien

Re: [mantisbt-dev] New mantisbt plugin

[Damien R. <dr...@ma...>]

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] New mantisbt plugin

[Максим К. <max...@gm...>]

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

Re: [mantisbt-dev] Report crashes to MantisBT via ABRT

[Damien R. <dr...@ma...>]

Hello Matej,

Thanks for the information.

I had a quick look at your wiki, and found that you're referencing an 
outdated release 1.3.0-beta.1 - In case you didn't know, beta.3 was 
released in September, and it includes your SOAP API changes. You might 
want to update your documentation accordingly.

Best regards
Damien


On 2015-12-03 16:59, Matej Habrnal wrote:
> Hi everyone,
>
> let me briefly introduce myself. I am Matej Habrnal and I work at Red Hat in
> ABRT [1] (Automatic Bug Reporting Tool) team. ABRT is a set of tools to help
> users detect and report application crashes. Its main purpose is to ease the
> process of reporting an issue and finding a solution.
>
> More than a year ago, I developed ABRT's plugin which allows report
> detected crashes into MantisBT. Also, I sent some patches to MantisBT which
> extended MantisBT SOAP API.
>
> The main reason for developing the plugin was that CentOS7 uses
> MantisBT as their bug tracking tool and there wasn't
> a way to report crashes detect by ABRT to CentOS's Bug Tracker (MantisBT).
>
> ABRT's MantisBT plugin is more then a year in use and CentOS7 users report
> the crashes via the reporter directly to https://bugs.centos.org. All ABRT's
> reports are prefixed with '[abrt]', so you can find them easily.
>
> I wanted to let you there is a client tool which is capable to open bug reports in MantisBT.
> The tool is packaged for CentOS7, RHEL7 and Fedora22 and higher and there are also some efforts to package it for openSUSE.
>
> ABRT is an opensource project which lives on GitHub [2] and is installed on Fedora,
> CentOS7 and RHEL7 by default. The sources of the mantisbt reporter are
> placed in [3,4] (libreport is ABRT's library providing API for reporting).
>
> Package which ships the mantisbt reporter is 'libreport-plugin-mantisbt'.
> Some information how to configure MantisBT and the reporter itself can be found on
> libreport GitHub's wiki [5].
>
> Feel free to send an email to mailing list cra...@li...
> or use IRC channel: #abrt @ irc.freenode.net to get more information.
>
> Regards
> Matej
> ABRT team
>
> [1] https://abrt.readthedocs.org/en/latest/
> [2] https://github.com/abrt
> [3] https://github.com/abrt/libreport/blob/master/src/plugins/reporter-mantisbt.c
> [4] https://github.com/abrt/libreport/blob/master/src/plugins/mantisbt.c
> [5] https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT
>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>

[mantisbt-dev] Report crashes to MantisBT via ABRT

[Matej H. <mha...@re...>]

Hi everyone,

let me briefly introduce myself. I am Matej Habrnal and I work at Red Hat in
ABRT [1] (Automatic Bug Reporting Tool) team. ABRT is a set of tools to help
users detect and report application crashes. Its main purpose is to ease the
process of reporting an issue and finding a solution.

More than a year ago, I developed ABRT's plugin which allows report
detected crashes into MantisBT. Also, I sent some patches to MantisBT which
extended MantisBT SOAP API.

The main reason for developing the plugin was that CentOS7 uses
MantisBT as their bug tracking tool and there wasn't
a way to report crashes detect by ABRT to CentOS's Bug Tracker (MantisBT).

ABRT's MantisBT plugin is more then a year in use and CentOS7 users report
the crashes via the reporter directly to https://bugs.centos.org. All ABRT's
reports are prefixed with '[abrt]', so you can find them easily.

I wanted to let you there is a client tool which is capable to open bug reports in MantisBT.
The tool is packaged for CentOS7, RHEL7 and Fedora22 and higher and there are also some efforts to package it for openSUSE.

ABRT is an opensource project which lives on GitHub [2] and is installed on Fedora,
CentOS7 and RHEL7 by default. The sources of the mantisbt reporter are
placed in [3,4] (libreport is ABRT's library providing API for reporting).

Package which ships the mantisbt reporter is 'libreport-plugin-mantisbt'.
Some information how to configure MantisBT and the reporter itself can be found on
libreport GitHub's wiki [5].

Feel free to send an email to mailing list cra...@li...
or use IRC channel: #abrt @ irc.freenode.net to get more information.

Regards
Matej
ABRT team

[1] https://abrt.readthedocs.org/en/latest/
[2] https://github.com/abrt
[3] https://github.com/abrt/libreport/blob/master/src/plugins/reporter-mantisbt.c
[4] https://github.com/abrt/libreport/blob/master/src/plugins/mantisbt.c
[5] https://github.com/abrt/libreport/wiki/Reporting-to-CentOSBT

Re: [mantisbt-dev] v1.3 changelog ?

[Roland B. <ro...@at...>]

Start reading
https://www.mantisbt.org/blog/?p=416
https://www.mantisbt.org/blog/?p=425

Roland

> Louis BAYLE <lba...@gm...> hat am 13. November 2015 um 17:45
> geschrieben:
> 
> 
> Hi,
> I don't know when you plan to release v1.3 but I would like the
> CodevTT plugin to be ready when it comes out.
> 
> So far, i noticed that the configuration files have moved to another
> directory, and when upgrading from 1.2 to 1.3beta the installer
> updated the DB.
> So there are some changes that I need to be aware of.
> 
> Is there a changelog from 1.2 to 1.3 available (architecture & features) ?
> 
> Thank you very much,
> best regards,
> 
> Louis BAYLE
> http://codevtt.org
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev

[mantisbt-dev] v1.3 changelog ?

[Louis B. <lba...@gm...>]

Hi,
I don't know when you plan to release v1.3 but I would like the
CodevTT plugin to be ready when it comes out.

So far, i noticed that the configuration files have moved to another
directory, and when upgrading from 1.2 to 1.3beta the installer
updated the DB.
So there are some changes that I need to be aware of.

Is there a changelog from 1.2 to 1.3 available (architecture & features) ?

Thank you very much,
best regards,

Louis BAYLE
http://codevtt.org