[design] Resolve concurrent save conflicts in React editor.

Description

In the GWT editor, when someone else saves a translation for the text flow that a translator is editing, the translator is shown a dialog that allows them to choose whether to discard what they have typed, or continue working on it.

The purposes are to ensure that a translator does not accidentally overwrite someone else's recent translation, and to make sure translators do not lose their work-in-progress when someone else saves.

This functionality or similar functionality that serves the same purposes should be added to the React editor.

Design
Storybook

Attachments

3

Activity

Show:

Former user 3 December 2017 at 23:56

Yeah that makes more sense
Maybe Use latest and Use original - since mine could be confusing if the other revision was made by the same person.

Former user 3 December 2017 at 23:53

The design looks good.

In the resolve conflict modal, instead of "Save and overwrite", and "overwrite", would it be simpler with "Use the latest", and "Use mine"?

Former user 3 May 2017 at 04:06
Edited

Add functionality to modify revision before saving - save & overwrite
Replace 'Needs work' etc with 'Resolve Conflict'

Former user 21 April 2017 at 04:26

It should be better, perhaps still red is ok too. Maybe like a police line or something

Making it editable may have other consequences I don't see, not sure.

Former user 21 April 2017 at 03:57


The label is part of the design to tell users that there is a conflict with that translation that must be resolved. I will make it smaller and not red, so it does not seem like an error. Do you think that would resolve this? I just want to make sure it is clear that the current segment is in a conflicting state.

I was thinking of making it not editable, but it makes sense that they would want to make further changes before resolving the conflict.

And use theirs/yours sounds much better!

Ready for Release

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Priority

More fields

Created 28 July 2015 at 23:09
Updated 27 June 2018 at 02:12
Resolved 9 May 2017 at 22:52