Jenkins telling me invalid issue key when it isn't

Sorry, I can’t provide Jenkins details, I don’t have access to the script console.
The question is this:
I have a script that creates a branch from our controller branch, makes some changes and then tries to add and commit those changes.
It doesn’t work, and I get an issue key error, where there is no issue key error:
remote:
[Issue Key check]
21:54:16 remote: The branch name “feature/EAPPS-439-update-prepare_beta_build.sh-and-add-new-script-to-point-to-prod-cc-beta-build-Sports-cloud-config” does not contain a valid issue key
21:54:16 remote:
21:54:16 To ssh://bitbucket.kindredgroup.com:7999/eapps/kindrediosapps.git
21:54:16 ! [remote rejected] feature/EAPPS-439-update-prepare_beta_build.sh-and-add-new-script-to-point-to-prod-cc-beta-build-Sports-cloud-config → feature/EAPPS-439-update-prepare_beta_build.sh-and-add-new-script-to-point-to-prod-cc-beta-build-Sports-cloud-config (pre-receive hook declined)
21:54:16 error: failed to push some refs to ‘ssh://bitbucket.kindredgroup.com:7999/eapps/kindrediosapps.git’
21:54:16 % Total % Received % Xferd Average Speed Time Time Time Current
21:54:16 Dload Upload Total Spent Left Speed
21:54:16
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 847 0 0 100 847 0 4028 --:–:-- --:–:-- --:–:-- 4033
I have no understanding of what Jenkins does in an Issue Key Check, as it is just a set of options ticked, I think on BitBucket.
Could this be because I’m trying to commit in a script, or something related?

Any ideas much appreciated

This sounds very much like that you need to have a BitBucket Issue Key in your Git commit comments before the BitBucket server will allow you to push your changes.

In theory, it should be able to tell you that you have an issue key in feature/EAPPS-439-... but I would guess that it is also expecting that EAPPS-439 is present in the commit message itself.

Thanks, Ken. That is indeed required, but it IS included in the commit message. I double checked by defining the text of the commit message and getting it to print that out to the console before using it in the actual commit. That’s what’s got me perplexed. I can’t see why it would fail.

This may very well be a bitbucket issue rather than a Jenkins issue

Good point. I’ll try this over there too.