TM Merge no longer has "Next Condition"

Description

In 4.2.1, TM merge no loner has "Next Condition" action option.
This means that we can either do not copy or copy as fuzzy.
We are not able to copy as translated, which is not desirable.

Could you please bring back the third action?

Focus on version merge first

Storybook - done

Activity

Show:
Alex Eng
July 24, 2017, 1:55 AM

After discussion with , their use case is to leverage as much translations as possible across whole Zanata to minimise the untranslated strings. Their required options (threshold, language selection) fits nicely with https://zanata.atlassian.net/browse/ZNTA-1865. The only missing piece right now is the "Next condition".

Kathryn Gough
August 2, 2017, 6:13 AM

Interesting approach - one of the more legible sketchy scribbles I've seen! While columns are usually used for comparisons, I will mock this up (alongside other variations) as it may be much easier for users to see what is going on with the options in their respective columns. Good stuff.

David Mason
August 2, 2017, 6:32 AM

does the toggle at the top of the "Imported TM" column cover the "don't copy" option? That option would effectively turn off "Imported TM" as an input to the process, so it may be more intuitive to turn it off at the top there and make the whole column appear disabled.

It also raises the question, why can't you switch off project translations as an input (if you want to use only the imported TM strings)?

Kathryn Gough
August 2, 2017, 7:05 AM
Edited

, good points. Yes the toggle at the top will cover that option, and it will be off by default and Projects will be active. When Imported TM is toggled on, then the Projects column will be disabled. I think this is the best idea since they are mutually exclusive.

Ready for Release

Assignee

Kathryn Gough

Reporter

ykatabam

Labels

Tested Version/s

None

Story Points

3

Sprint

None

Fix versions

Priority

Medium
Configure