Design: Redesign Version Merge feature
Activity
Show:
Former user 3 May 2017 at 04:42
Remove match percentage for meantime
Former user 7 April 2017 at 05:39Edited
Good idea . I shall bring it up in the next sprint retrospective
Former user 7 April 2017 at 05:28Edited
looking good. We might need to run through the scnerio on make sure this covers what is needed.
Former user 6 April 2017 at 08:35
, can I get your thoughts on these updated mockups?
Just want to know if I can go ahead and mark this issue as Completed.
Completed
Details
Details
Assignee
Former userReporter
Former userLabels
Tested Version/s
None
Components
Sprint
None
Priority
unspecifiedMore fields
Time tracking
More fields
Time trackingCreated 29 March 2017 at 23:37
Updated 3 May 2017 at 04:58
Resolved 3 May 2017 at 04:58
The current version merge feature allows maintainers to merge between two project versions. The translations that are merged are those with an exact match.
This feature needs to be extended, by allowing the version merge modal to also handle:
merges across multiple projects and versions
different match percentage thresholds
The reason for this is so all untranslated words can be sent to the translation agency.
By clicking the version merge button in the versions menu, a modal will pop up. I need to mock this up and add the frontend code (react-bootstrap) for this issue.
Rough examples
If match threshold is not changed (default is 100%), then no directory tree of projects will show.
There will be only a list of versions for the current project - so that only 2 versions can be merged. This is the same functionality as the current version merge feature.
If the match threshold is changed from 100%, then the directory tree will show, expanding only the active directory initially (to save modal space), allowing maintainers to select multiple versions across multiple projects to merge. This directory tree will have a vertical scroll so that it does not increase the height of the modal too much.