• 0
    • 1
    • We collect Confluence 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      When an edit conflict occurs, we should provide a proper, interactive merge resolution tool instead of the current confusing "do it yourself in this big edit window" approach.

      Tricky? Yes. Impressive if we got it working? Absolutely.

            [CONFSERVER-11734] Provide a proper 3-way merge tool for edit conflicts.

            A better conflict resolution process is badly needed. 

             

            Smart GIT's conflict reoslution was/is a good standard to look at. 

            Colin Sanders added a comment - A better conflict resolution process is badly needed.    Smart GIT's conflict reoslution was/is a good standard to look at. 

            Editing conflicts and lost changes (due to overwrites and people not even noticing) is the one biggest usability problem for us in Confluence. Please revisit this issue.

            Stefan Braunewell added a comment - Editing conflicts and lost changes (due to overwrites and people not even noticing) is the one biggest usability problem for us in Confluence. Please revisit this issue.

            We are using Confluence and often suffering from editing conflicts.
            3-way merge like MediaWiki is absolutely necessary.

            Do you have a roadmap to implement this feature?

            Haruka Iwao added a comment - We are using Confluence and often suffering from editing conflicts. 3-way merge like MediaWiki is absolutely necessary. Do you have a roadmap to implement this feature?

            Dan Amitai added a comment -

            I'm also interested in seeing this as a feature.

            Why not license the solution from a company that implemented (and did so well enough) - like P4?
            I'm sure you can devise some partnership with them to acquite an excellent merging ability and then integrate it into your product.

            Dan

            Dan Amitai added a comment - I'm also interested in seeing this as a feature. Why not license the solution from a company that implemented (and did so well enough) - like P4? I'm sure you can devise some partnership with them to acquite an excellent merging ability and then integrate it into your product. Dan

            I would also be very interested to see this feature implemented. It doesn't seem to matter how many times I ask people to not edit whilst someone else is in the page - they still do it!

            smarlowWWF added a comment - I would also be very interested to see this feature implemented. It doesn't seem to matter how many times I ask people to not edit whilst someone else is in the page - they still do it!

            I would also love to see this feature. As an illustrative example, take a look at how perforce's programmers solved this issue ... very transparent and nice to look at!

            Andreas van Rienen added a comment - I would also love to see this feature. As an illustrative example, take a look at how perforce's programmers solved this issue ... very transparent and nice to look at!

            Thanks so much for adding this. On several occasions I've had to decide whether to cancel my changes or trash someone else's. Having the option to merge them would be a great alternative!

            Bill Callahan added a comment - Thanks so much for adding this. On several occasions I've had to decide whether to cancel my changes or trash someone else's. Having the option to merge them would be a great alternative!

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              52 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: