nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

make jira issue mandatory during commit or pull request

unknown

Hello Community,

Need help please

For better tracebiliy ,we want to make sure developers mentioned jira issue number dueing commit or pull request

How can we achieve it in bitbucket cloud

I am new to bitbucket , so please excuse if this is a simple question

Thanks

Accepted answers

Theodora Boudale

Hi @[deleted],

There is a setting on the repository level to require an issue key in commit messages.

Can you please confirm if you are using Jira Cloud? If so, the first step is to double-check if the Bitbucket workspace that owns the repos you are working on, is already integrated with your Jira Cloud instance (and if not, integrate them).

Log in to https://bitbucket.org/
Select your avatar > All workspaces
Select the workspace that owns the repos your team is working on
Select the option Settings from the sidebar (you'll need to be an admin of the workspace to see this option)
Then select Jira from the new sidebar

If you see the Jira Cloud instance you use listed there, with the option Disconnect, it means the integration is already in place. Otherwise, you will see a link Connect. You can use that to make the integration (you'll also need to be an admin in Jira to perform this).

After you confirm that the integration is there:

Open a repository of this workspace in your browser
Select from the sidebar > Repository settings > Links
You should be able to see some Read-only links for Jira. You will also see an option Require issue keys in commit messages. If you enable that, users will not be able to push any commits that don't have an issue key in their commit message.

We don't have a setting to require an issue key in PR titles and/or description. There is a feature request about this in our issue tracker that you can vote for if you'd be interested in that:

https://jira.atlassian.com/browse/BCLOUD-20353

I'd like to mention here that if a PR is created without referencing an issue key, but the commits of the source branch have issue keys in their messages, then this PR will still be displayed in the respective issues in Jira.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

All comments

Theodora Boudale

Hi @[deleted],

There is a setting on the repository level to require an issue key in commit messages.

Log in to https://bitbucket.org/
Select your avatar > All workspaces
Select the workspace that owns the repos your team is working on
Select the option Settings from the sidebar (you'll need to be an admin of the workspace to see this option)
Then select Jira from the new sidebar

After you confirm that the integration is there:

Open a repository of this workspace in your browser
Select from the sidebar > Repository settings > Links
You should be able to see some Read-only links for Jira. You will also see an option Require issue keys in commit messages. If you enable that, users will not be able to push any commits that don't have an issue key in their commit message.

We don't have a setting to require an issue key in PR titles and/or description. There is a feature request about this in our issue tracker that you can vote for if you'd be interested in that:

https://jira.atlassian.com/browse/BCLOUD-20353

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

unknown

Thanks @Theodora Boudale for such a nice and details description

I will try the steps mentioned and update you

Thanks

Ashish

Theodora Boudale

You are welcome Ashish, I'll wait to hear your update then!

unknown

@Theodora Boudale : Hi Theodora . i tried the solution and it worked

However , it is also allowing invalid jira issues as well in the commit

For example : I have AC-5 as a valid jira issue and it allows commit

When i try with AC-55 , this issue is not available in jira itself ..still it allows the commit

How can we avoid invalid issues during commit

Can you please advice

Thanks
Ashish

Tamir Melamed

Is it also possible with GitHub?

Theodora Boudale

Hi Tamir,

I'm not aware of that. The repository links and the option "Require issue keys in commit messages" are a Bitbucket feature and the links are not limited to Jira. You can reach out to GitHub support team to ask if such a feature is available in GitHub.

Kind regards,
Theodora

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

atl-orange