Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-5658

Option to reject commits without an issue key in their message (BB-2415)

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hi,

      We recently went from Jira OnDemand SVN to Git on BitBucket.

      One thing we miss alot, is the ability to demand users entering a Jira issue key, when checking in code.

      I know that Git is distributed, and a lot of the checkin/commit stuff is handled locally.
      But if i Jira issue check was done by BitBucket, no code could be added to "final destination" without an Jira issue key defined in the commit description.

      So this feature request is, that you possibly come up with a clever idea for this :o)

      Best regards
      Peter Meyer

          Form Name

            [BCLOUD-5658] Option to reject commits without an issue key in their message (BB-2415)

            Attachment 1679583198-bitbucket-vote.png has been added with description: Originally embedded in Bitbucket issue #5658 in site/master

            Brett Cave added a comment - Attachment 1679583198-bitbucket-vote.png has been added with description: Originally embedded in Bitbucket issue #5658 in site/master

            Would it be possible to add this as part of the branch permissions instead of a global repo policy? We’d like to loosen the policy enforce Jira keys to be set only on the master branch.

            Dustin Row added a comment - Would it be possible to add this as part of the branch permissions instead of a global repo policy? We’d like to loosen the policy enforce Jira keys to be set only on the master branch.

            What is the correct way to define multiple allowed Jira issue key names on the “Links“ page in the repository settings? Is it possible?

            Michał Janicki added a comment - What is the correct way to define multiple allowed Jira issue key names on the “Links“ page in the repository settings? Is it possible?

            TJ added a comment -

            @kristianaasen @florin05 There is a plugin for Bitbucket Server that does this - https://marketplace.atlassian.com/plugins/com.midori.bitbucket.plugin.commitpolicy/server/overview . There are some caveats to this solution as I believe it is JIRA only and requires a non-free JIRA plugin to use. If this doesn't work for you, feel free to comment on the open issue here that the server team is looking at - https://jira.atlassian.com/browse/BSERV-9884

            TJ added a comment - @kristianaasen @florin05 There is a plugin for Bitbucket Server that does this - https://marketplace.atlassian.com/plugins/com.midori.bitbucket.plugin.commitpolicy/server/overview . There are some caveats to this solution as I believe it is JIRA only and requires a non-free JIRA plugin to use. If this doesn't work for you, feel free to comment on the open issue here that the server team is looking at - https://jira.atlassian.com/browse/BSERV-9884

            florin05 added a comment -

            @tj_kells Same question here, is this rolled out for the on premises server ? We use v5.4.1 and I don't see it.

            Surprised you don't have a good/transparent way to assign issues releases. That is your business after all.

            florin05 added a comment - @tj_kells Same question here, is this rolled out for the on premises server ? We use v5.4.1 and I don't see it. Surprised you don't have a good/transparent way to assign issues releases. That is your business after all.

            @tj_kells Is this rolled out for server? Or only for cloud? Runing Server 5.3.1.

            Kristian Aasen added a comment - @tj_kells Is this rolled out for server? Or only for cloud? Runing Server 5.3.1.

            aamelkin added a comment -

            Ferenc, thank you. I've recently been pointed to that plugin already just to find that despite it being free, it requires a significantly pain JIRA counterpart plugin to work. If anyone is interested, I have a maybe-not-so-elegant-and-integrated but completely free solution that I described here: https://stackoverflow.com/questions/16091516/git-server-side-update-hook-in-bitbucket/44966631#44966631

            In short, it's a real update hook for Bitbucket Server's backend git instance. The hook is written in shell and node.js and is completely open-source.

            aamelkin added a comment - Ferenc, thank you. I've recently been pointed to that plugin already just to find that despite it being free, it requires a significantly pain JIRA counterpart plugin to work. If anyone is interested, I have a maybe-not-so-elegant-and-integrated but completely free solution that I described here: https://stackoverflow.com/questions/16091516/git-server-side-update-hook-in-bitbucket/44966631#44966631 In short, it's a real update hook for Bitbucket Server's backend git instance. The hook is written in shell and node.js and is completely open-source.

            Midori added a comment -

            Midori added a comment - Alexander, for Bitbucket Server, see: https://marketplace.atlassian.com/plugins/com.midori.bitbucket.plugin.commitpolicy/server/overview

            aamelkin added a comment -

            Is this feature available in Bitbucket Server? I don't see any 'Links' at all in repository configuration pages. The only thing about links that I have in Bitbucket Server is 'Application Links' in global configuration.

            We really need a hook to validate commit messages against our policy or at least against JIRA for issue existense.

            We're using Bitbucket Server 5.0.1

            aamelkin added a comment - Is this feature available in Bitbucket Server? I don't see any 'Links' at all in repository configuration pages. The only thing about links that I have in Bitbucket Server is 'Application Links' in global configuration. We really need a hook to validate commit messages against our policy or at least against JIRA for issue existense. We're using Bitbucket Server 5.0.1

            Thanks guys!

            Brett Cashman added a comment - Thanks guys!

              tkells TJ
              legacy-bitbucket-user Legacy Bitbucket Cloud User (Inactive)
              Votes:
              190 Vote for this issue
              Watchers:
              135 Start watching this issue

                Created:
                Updated:
                Resolved: