You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In Bitbucket, when linked with Jira (or other supported Issue Trackers), you can enable the option to require commit message to contain an issue key. This way, developers are forced to reference their Jira issue, and all commits can be then tracked and reviewed from Jira.
Not all commits come from developers in our case. We have cases where Bamboo performs commits, along with another build platform, for various reasons, like adding labels or changing Maven settings.
Is there a way to add exceptions? Where some users or SSH keys don't have that requirement? That way tasks from Bamboo or Jenkins could be permitted to push changes without a Jira issue.
Hi, @Curtis, thank you for reaching out to Atlassian Community.
Currently, it’s not possible to exclude CI tools from requiring a Jira Issue key on commit messages, but we already have a feature request to implement that:
I would suggest that you add your vote there (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.
You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.