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

Add ability to link previous commits to existing JIRA issues (BB-10211)

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.

      Smart commits is an excellent feature to link BitBucket commits - and the code changes - to JIRA issues. However, if a user forgets to add the issue key to the commit and then pushes upstream, it's very hard (without breaking the git repo for others) to add the issue key to the commit message. It would therefore be very useful to be able to manually link an earlier commit - and its code - to an existing JIRA issue, as if the issue key had been included in the commit message.

      The commit message doesn't need to be changed, but the code changes and commit ID should be added to the issue.

      This could be done with a separate UI to attach JIRA issues to an existing commit. When displaying JIRA issues, in addition to searching in the commit message, it would also search the new JIRA-issue-and-commit association configured via the new UI.

      The same thing could be applied to branches. Pull requests might be fine, as we could easily update the pull request title to include the issue key.

          Form Name

            [BCLOUD-9470] Add ability to link previous commits to existing JIRA issues (BB-10211)

            Evan Bovie added a comment -

            I really think this should be reopened. In the meantime, vote for this issue that's still open for renaming PRs after they've been merged: BCLOUD-15190

            Just needed this again today, and saw that I already commented on the issue over a year ago. 

            Evan Bovie added a comment - I really think this should be reopened. In the meantime, vote for this issue that's still open for renaming PRs after they've been merged:  BCLOUD-15190 Just needed this again today, and saw that I already commented on the issue over a year ago. 

            evanbovie added a comment -

            bump

            evanbovie added a comment - bump

            Andrés Julián Aristizábal Martínez added a comment -

            We want this functionality too

            Andrés Julián Aristizábal Martínez added a comment - We want this functionality too

            Matt Sundquist added a comment -

            We really need this feature.

            Matt Sundquist added a comment - We really need this feature.

            mike_noe added a comment -

            I agree this is still a major issue.

            mike_noe added a comment - I agree this is still a major issue.

            Anton Ukhanev added a comment -

            How is this closed? And with priority major??

            Anton Ukhanev added a comment - How is this closed? And with priority major ??

            Legacy Bitbucket Cloud User (Inactive) added a comment -

            This issue has been closed due to inactivity. If you continue to see problems, please reopen or create a new issue.

            Legacy Bitbucket Cloud User (Inactive) added a comment - This issue has been closed due to inactivity. If you continue to see problems, please reopen or create a new issue.

            Legacy Bitbucket Cloud User (Inactive) added a comment -

            We are using bitbucket as well and are not able to correct a commit that had the wrong key entered. The dev entered 51 instead of 15 which is likely to happen often. How do you fix it?

            Legacy Bitbucket Cloud User (Inactive) added a comment - We are using bitbucket as well and are not able to correct a commit that had the wrong key entered. The dev entered 51 instead of 15 which is likely to happen often. How do you fix it?

            Andrae Muys (Inactive) added a comment -

            This is important, but just as important is the ability to unlink a commit from an issue where the wrong key has been included in the comment by mistake.

            Andrae Muys (Inactive) added a comment - This is important, but just as important is the ability to unlink a commit from an issue where the wrong key has been included in the comment by mistake.

              Unassigned Unassigned
              3b065ac34ef3 zehualiu
              Votes:
              7 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: