how to support custom Jira Issue key in the Scriptrunner for BitBucket

I'm adding a pre-receive hook on my repository in Bitbucket.

I added the "Require commits to be associated with a JIRA issue" hook. It is provided by ScriptRunner.

But when I push the master branch the hook doesn't recognize the custom Jira issue key.

For example: my Jira issue key in the commit comment is "A123B-123" and the status is "Work".

I get the below errors when running "git push" .

remote: =====================================================================
remote: One or more JIRA issues from your commits not found by query (status in ("work")):
remote:
remote: Ref: 3240b5d895b - B-123
remote: =====================================================================
remote:

Anyone has the similar issue and knows how to resolve it?

1 answer

0 vote

Is there a particular reason your using a custom issue key?

ScriptRunner for Bitbucket Server only supports the official JIRA issue key pattern described here.

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

710 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot