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

Fygo Cui October 30, 2017

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 votes
adammarkham
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 6, 2017

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 Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events