@David Benson [draw.io] also interested in this. In the interim, is there any thought towards highlighting / identifying / Locking (always a dangerous feature) items edited by someone else.
First case today where someone came a cropper from editing separate pages with someone else. Managed to repair thanks to version history, at least. I know it will happen again, as people see something in Confluence and assume collaborative editing.
We have discussed whether there's an interim solution. The thing is, we have the conflict resolution algorithm done (we cleared out the last issue about a week ago), what's left is back-end code to manage the locking. Once we have that, we have collaboration done.
I fully agreed last-write wins is really bad, but we're not that far away (relative to the age of this thread) from a point where we can start showing you concurrent editing. The locking style solutions, as you say, are actually really hard to implement in a safe way. The quickest route, at this point, is to just do the whole thing.
Actually, I lied. There was a really easy way to prevent last write wins, this will go into the next release (hopefully, next week).
What will happen now is if you save and another write has occurred since you opened for editing, you will be offered the chance to merge in the changes before saving again.
The merge algorithm is a proper intelligent merge, not an overwrite.
My next question for everyone is what % this fixes your problem vs what % importance true real time collaborative editing is?
@David Benson [draw.io] even better!
For us (in context Confluence as an Intranet launched last month for 300 people, with only 30 or so (currently) clued up on Draw IO): 90% of the issues will be fixed by merge (assuming it is intelligent and that people's drafts they never edited don't count to the total).
Ask me in a year's time when I have banged the drum a bit more about our collaborative software, and more people have the chance to extract value, then maybe it changes. But generally for me this is catching the edge cases where last-write wins.
However, all that being said, if I could 'whiteboard' in meetings with Draw IO, with several people able to chip in on their laptops, then it would likely take off
Merging went into the last version. So, if you go to save and someone else has saved since you loaded, a merge will take place of your and their. If that's not a good thing, select all, copy, merge, and paste yours back over.
We've also added File->Synchronize in the draw.io editor menu. This gives you a way to manually sync saved changes from another user.
The problem part is still how to give real time notifications in a way that cannot affect Confluence performance.
re needs: Currently we use both draw.io and miro (previously realtimeboard).
They are distinct but ideally, you want the concurrent editing as provided by miro, yet good/decent editing as in draw.io.
I think re problem solved, I look at concurrent text editing as an indicator. It has taken alot of time to take off, to have become comfortable for alot of people and to be commonly utilized - and it is still not, I would say. So its a shift in culture for alot of companies (some would likely find it more natural).
I think the same shift will come, albeit slowly for concurrent visual manipulation.
I attended Atlassian Summit 2019 and learned a lot from the presenters, attendees and knowledgeable Atlassian product managers. The presentations I attended focused on applying Agile, pla...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events