Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4986

Don't associate a PR with a JIRA issue based on merge commit messages

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Pull Requests
    • None
    • 0
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      If I merge from my target branch into a feature branch that is in a pull request (e.g. from master into feature/ISSUE-1), using "git merge --log", it includes the commit messages from all the new work on master in the merge commit.
      Stash then shows all the issues from those commits being associated with the PR in the Stash UI.
      In this case this is wrong - I have simply made my feature branch as up-to-date as possible and the PR has nothing to do with those issues.

          Form Name

            [BSERV-4986] Don't associate a PR with a JIRA issue based on merge commit messages

            There are no comments yet on this issue.

              Unassigned Unassigned
              mwatson@atlassian.com mwatson
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: