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

Ability to reject commit without an issue key but only for selected branches

XMLWordPrintable

    • 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-21520] Ability to reject commit without an issue key but only for selected branches

            Karol Wieraszka added a comment - - edited

            I could clone an issue but I can't modify description :O

            Anyway, We would really be interested in ability to reject pushing/merging PRs if the commit message does not contain ticket ID, but only for selected targets e.g. master.

            There is an option in Repository settings to `Require issue keys in commit messages` but this does not work in our workflow. We use squash when merging PRs to master and we don't care if these `temporary` commits have the ticket id, as long as final squashed commit will have it.

            Karol Wieraszka added a comment - - edited I could clone an issue but I can't modify description :O Anyway, We would really be interested in ability to reject pushing/merging PRs if the commit message does not contain ticket ID, but only for selected targets e.g. master. There is an option in Repository settings to `Require issue keys in commit messages` but this does not work in our workflow. We use squash when merging PRs to master and we don't care if these `temporary` commits have the ticket id, as long as final squashed commit will have it.

              tkells TJ
              5487d7507039 Karol Wieraszka
              Votes:
              7 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: