-
Bug
-
Resolution: Fixed
-
High
-
5.1, 5.1.2, 5.1.3, 5.1-OD-6, 5.2-OD-5
-
None
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
As per the documentation, Confluence should be able to merge non-conflicting changes successfully when two users are editing a page at the same time, but this doesn't seem to be happening.
Steps to reproduce:
1- User 1 opens page for editing, and enters text in one section:
2- User 2 opens page for editing, and enters text in another section:
3- User 1 saves changes, and gets the resulting page:
4- User 2 saves changes, and gets the resulting page:
The changes made by User 1 were lost, even though they were not conflicting. No errors are shown during the process.
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CONFSERVER-29048] Confluence fails to non-conflicting merge changes while editing page concurrently
Hi Don, sorry if this comment should go in a different place. Please see also the comments from others experiencing this now, right above mine. Where would be the right place to post this concern? When you say contact support, help me understand: I thought the bug system is support for Atlassian? That's certainly how I've been using it. If there a traditional support intermediary, why let us post here directly?
Bruce Cannon
added a comment - - edited Hi Don, sorry if this comment should go in a different place. Please see also the comments from others experiencing this now, right above mine. Where would be the right place to post this concern? When you say contact support, help me understand: I thought the bug system is support for Atlassian? That's certainly how I've been using it. If there a traditional support intermediary, why let us post here directly? Hi Bruce. Thanks for contacting us. That's terrible to hear. The issue you've commented on is about a specific behaviour with Confluence 5.1. It was resolved years ago. What you're describing sounds new. Please contact support to figure out what's happening.
Bruce Cannon
added a comment - Losing edits when co-editing is definitely not resolved. Just lots a bunch of important co-work today. No auto-save instances of pages appear in history during periods of co-editing. Or, if they ever existed, they were deleted during the merge process, leaving only the history entry for the person who saved first. Please re-open; and also please change your messaging which implies that merging is a feature, it is emphatically not.
Bruce Cannon
added a comment - Losing edits when co-editing is definitely not resolved. Just lots a bunch of important co-work today. No auto-save instances of pages appear in history during periods of co-editing. Or, if they ever existed, they were deleted during the merge process, leaving only the history entry for the person who saved first. Please re-open; and also please change your messaging which implies that merging is a feature, it is emphatically not. Can this be re-opened or a new issue raised as we are experiencing this with Confluence 5.8.4
Hi,
We have 5.7.1 and this is happening with our instance also.
Kind Regards,
Om
Martin Morrey
added a comment - Could you update the documentation for 5.1- to reflect the fact that this feature is broken in this version?
Martin Morrey
added a comment - Could you update the documentation for 5.1- to reflect the fact that this feature is broken in this version? Hi gary15,
I'm sorry and surprised to hear you are still hitting this. The fix for this bug landed on OD months ago. The additional changes John said were due in 5.4 also landed weeks ago, but did not relate to this bug as such.
If you are having this exact behaviour in your current OD instance please file a support ticket, as that is very surprising and needs investigation.
If you're having different merging issues please raise a new issue here, or similarly file a support ticket.
Thanks,
Don
Gary Barbon
added a comment - Hi John. We're approaching the end of the hopeful target month and, to the best of my knowledge, this resolution has not been applied to the AtlassianOnDemand instances yet (as I'm still having this issue today). Is there an ETA for application to AOD?
Gary Barbon
added a comment - Hi John. We're approaching the end of the hopeful target month and, to the best of my knowledge, this resolution has not been applied to the AtlassianOnDemand instances yet (as I'm still having this issue today). Is there an ETA for application to AOD? 
Hi Bruce, https://support.atlassian.com is where to go for direct support, where dedicated support engineers will help with any problems you have. jira.atlassian.com is for specific bugs against specific versions.
You can file bugs here at JAC, and we love customers to do that, but you'll get much faster responses on SAC usually.
Commenting on issues that have been resolved won't usually garner much response unless somebody is watching the issue.