Issue #3750 new

Issue service adds multiple issue comments when you have multiple branches (BB-3746)

Dylan Etkin avatarDylan Etkin created an issue

If you create a new branch that shares commits with another branch and there are issue references in that branch the issue service adds multiple comments. It should only ever add one.

Comments (6)

  1. Hendy Irawan

    Thanks Brian.

    I can't create another branch until this issue is resolved.

    For a quick fix, can you provide an option to disable commit links (temporarily). So I can disable it, create a new branch(es), then re-enable it afterwards.

    The priority should be blocker because practically I can't push a branch before this issue gets resolved or at least we have a quick fix as I described above.

  2. Hendy Irawan

    My original issue description in #6360 :

    Creating a new branch re-parses all commits from the first commit and wreaks havoc on issue tickets.

    The proper solution is either: (or both, ie configurable, but should have sane defaults)

    1. Only parse the main branch (e.g. "master" as configured)
    2. Only parse new commits (not already existing in the repository). Existing commits should not be reparsed.

    Commit links should also be configurable, so it can be disabled/enabled at will.

  3. Hendy Irawan

    I just tested it a few minutes ago and buggy behavior still occur : bitbucket is reprocessing all the commits for the branch :

    Hendy Irawan
    changed status to resolved
    Fixed #1. README
     <<cset 14c9f1a94d17>>
    
    Edit  Mark as spam  Delete  3 minutes ago
    Hendy Irawan
    changed status to open
    harusnya gak diresolve lagi
    Edit  Mark as spam  Delete  3 minutes ago
    Hendy Irawan
    changed status to resolved
    Fixed #1. README
     <<cset 14c9f1a94d17>>
    
    Edit  Mark as spam  Delete  3 minutes ago
    

    Here's the test, it's on a public repo : https://bitbucket.org/hendyirawan/branchingtest/issue/1/yuhu

  4. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.