Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreBitbucket 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 ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.