We recently set up CircleCI's Jira notification tool. This allows us to track our CI/CD pipelines on each team's Jira Deployment page.
To facilitate this, we have to include a Jira story ID (e.g. "TO-128") in our PR titles or in a commit (merge commits excluded).
Is there anything BitBucket can do to enforce this? Either on commit messages - a Git hook for instance - or in PR titles?
Hi Duncan and welcome to the community.
It is possible to enforce this for commit messages (not for PRs I'm afraid).
If you have integrated your Bitbucket workspace with a JIRA instance, there will be a link for each workspace repo, which you can view from Repository settings > Links.
In the same page, there is an option Require issue keys in commit messages which you can enable for each repo. Is this something that works for you?
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events