Success

User tests: Successful: Unsuccessful:

avatar b2z
b2z
1 Mar 2015

See #590 for reference.

avatar b2z b2z - open - 1 Mar 2015
avatar b2z
b2z - comment - 2 Mar 2015

@mbabker did you miss it or you think that it is wrong implementation? I know that it is also project specific, but there is no other way currently how we can make JBS work easier...

avatar elkuku
elkuku - comment - 7 Mar 2015

I have not tested this in any way, but from what I can remember this code will not be executed if the issue is added by the hook controller thingy aka created on GitHub, or am I wrong here?

avatar b2z
b2z - comment - 7 Mar 2015

You are right. Then may be the right place for adding this label would be JoomlacmsIssuesListener?

avatar mbabker
mbabker - comment - 7 Mar 2015

That listener adds the label already for issues created on GitHub. The label isn't added for issues created in the application.

avatar b2z
b2z - comment - 7 Mar 2015

Why we can not use it to create the same label for CMS tracker?

avatar mbabker
mbabker - comment - 7 Mar 2015

Because the listeners aren't in use in the main controllers right now, they're only registered to the webhooks.

avatar b2z
b2z - comment - 7 Mar 2015

Right... So when an issue is created on GitHub this listener adds no code label back on GitHub. When issue is created in the application this listener does not run, then my commit is ok? :smile:

avatar mbabker
mbabker - comment - 7 Mar 2015

It's an ugly workaround but it would work. We really need to work on #596...

avatar mbabker mbabker - change - 7 Mar 2015
Status New Closed
Closed_Date 0000-00-00 00:00:00 2015-03-07 18:05:06
avatar mbabker mbabker - close - 7 Mar 2015
avatar mbabker mbabker - reference | - 7 Mar 15
avatar mbabker mbabker - merge - 7 Mar 2015
avatar mbabker mbabker - close - 7 Mar 2015
avatar mbabker mbabker - head_ref_deleted - 7 Mar 2015
avatar b2z
b2z - comment - 7 Mar 2015

It's an ugly workaround but it would work.

I know :(

Add a Comment

Login with GitHub to post a comment