Pushing new branch triggers comments to issues

Issue #5094 duplicate
Marcus Bertrand
staff created an issue

From a support issue:

I'm having a problem and I 'm not sure if it is a bug or if it is pilot error.

I recently started marking issues 'resolved' by including "Fixed #x" in my commit messages. This marks the issue resolved as expected. However, now any time I push a new branch to bitbucket each issue that was 'auto-marked' previously is auto marked again. Here is the workflow that reproduces this problem:

To summarize:

  1. Create local branch X
  2. Push branch X to origin
  3. Alter branch X locally
  4. Commit branch X locally with message that includes "Fixed #1" to mark issue 1 resolved.
  5. Push branch X to origin *** At this point, issue #1 is automatically marked resolved.
  6. Create and accept pull request to merge branch X with master
  7. Locally, checkout master and pull from origin
  8. Create new branch Y.
  9. Push branch Y to origin *** At this point, issue #1 is commented on again automatically It seems like the "Fixed #1" message is persisting somehow and each time I push a branch, it triggers another round of issue comments and emails. I'm using Git if that matters.

Comments (5)

  1. Marcus Bertrand staff reporter

    We tried to reproduce this issue and weren't able to. If you have any more information with some specific examples and screenshots and URLs, please report them to support.

  2. Brian Nguyen

    Apologies for the late reply, this issue fell off our radar.

    This issue has actually already been raised. I have closed this issue, but if you would like further updates please watch the linked issue.

  3. Log in to comment