RFE: Improve the [CopyTrans] options page, for clarity and accommodating the review feature


Description of problem:
Now there are 5 states as result of enabling review feature, they are:
"Untranslated", "Fuzzy", "Rejected", "Translated" and "Approved".

To avoid confusion, the copytrans option page should do following change:
1. Clearly states that all rules will be evaluated, and the "lowest" state will be choose.
2. Change the "Reject" to "Discard".
3. Rule 5 should be: if everything match and the translation is approved, then set as "Approved"
4. Rule 6 should be: otherwise set as "Translated".

Version-Release number of selected component (if applicable):
Zanata version 3.0.0-SNAPSHOT (20130523-1440)


Bugzilla Migration
July 31, 2015, 1:24 AM

Carlos Munoz commented on 2013-08-08 21:40:29 -0400:

I still think we should allow for detailed customization of the process (Just recently we were able to use copy trans to reuse translations in a very creative way for one of the projects).

But I like the idea of the "predefined" configurations for copy trans. So what if we offer some way to automatically make the right selections for "Software", "Documentation", and "Software (ignore doc name)" for the common cases. We could even hide the "advanced" options until the user specifically asks about them.

BTW, I think Luke's mockup is a great way of conveying the process.

Bugzilla Migration
July 31, 2015, 1:24 AM

Luke Brooker commented on 2014-03-04 23:28:29 -0500:

This has been iterated on for the new project screen. A mockup can be seen here:


I think this can still be improved in the future, but further improvements I have thought of would need more backend changes which can not be included this sprint.

Damian Jansen
September 1, 2016, 5:08 AM

The settings still don't indicate what happens with Approved and Rejected entries. Still valid.

Kathryn Gough
November 7, 2016, 9:16 PM


Alex Eng
April 20, 2018, 12:23 AM

We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.


Kathryn Gough


Ding-Yi Chen


Tested Version/s