Stash plugin “Tickets, Please!” is still working for Stash 2.9.4？

[yuxiang zhang]

Hi

We deployed stash 2.9.4 in our production environment, but we found "Tickets, Please" doesnot work properly that it will not reject any pushed commits even if there is no jira ticket magic code in the commit description. I can ensure that the related hook configuration have been configured.

could anyone help me to figure out if this plugin is still alive for Stash upstream versions?

[Greg Breen · Accepted solution]

I just deployed Tickets, Please! We're running Stash 2.12.1. TP is working, but I noticed two issues so far:

1) It keeps defaulting to "release/" in "Branch Namespace Enforcement" - even when I clear it, if I open the config again, it still says this (but it's not true).

2) If we make a new branch on our local, do some commits without JIRA issue keys, then push, TP doesn't reject it. But it will reject subsequent pushes that lack keys.

So I would say TP still works, but with limitations.

[yuxiang zhang]

Hi Greg,

So glad to see that there is an answer!

Thanks for your comments and listed limitation would be helpful for those using 2.12.x.

What happens on my side are more problematic than yours:

1）TP simply doesn't work and don't report any error indications, no matter it is a first branch push or 2nd push.

2）I also tried with "Use Application Link to connect to Jira", or use "Jira URL" and "Jira Username", and neither works.

3）TP doesn't work on my side since v2.7.2 our first installtion.

Maybe I will revisit this after ugprading to v2.12.x

[yuxiang zhang]

Hi Greg,

So glad to see that there is an answer!

Thanks for your comments and listed limitation would be helpful for those using 2.12.x.

What happens on my side are more problematic than yours:

1）TP simply doesn't work and don't report any error indications, no matter it is a first branch push or 2nd push.

2）I also tried with "Use Application Link to connect to Jira", or use "Jira URL" and "Jira Username", and neither works.

3）TP doesn't work on my side since v2.7.2 our first installtion.

Maybe I will revisit this after ugprading to v2.12.x