Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1000237

Summary: Copy Trans leaves translations in 'Untraslated' state but with content in them.
Product: [Retired] Zanata Reporter: Carlos Munoz <camunoz>
Component: Component-LogicAssignee: Carlos Munoz <camunoz>
Status: CLOSED CURRENTRELEASE QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.0CC: djansen, ykatabam, zanata-bugs
Target Milestone: ---   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-27 03:25:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Carlos Munoz 2013-08-23 04:00:36 UTC 
Description of problem:
In some scenarios, copy trans will leave translations in 'NEW' (untranslated) state but with some content.

Version-Release number of selected component (if applicable):
3.0, but it's probably also happening in the 2.x series.

How reproducible:
Sometimes. Depending on the data.

Steps to Reproduce:
1. Run copy trans on an empty project. Make sure the copy trans options include a "copy as fuzzy" option (this is the case that was encountered).
2. Check the copied translations.

Actual results:
Translations with content should be in either Fuzzy or approved state.

Expected results:
Some translations with content (successfully copied the right translation) were left in Untranslated state.

Additional info:
From these results, all the translations should have been in Fuzzy state, and were copied correctly (their source content matched). My theory is that it's a hole in the algorithm that calculates the end state of a copied translation.
Comment 1 Carlos Munoz 2013-08-30 03:49:46 UTC 
Some unwanted copy trans results were not being filtered out.

See:
https://github.com/zanata/zanata-server/pull/149
Comment 2 Carlos Munoz 2013-08-30 03:52:57 UTC 
Testing notes:

The best way to test this is to populate data that matches the executed copy trans, but is part of an obsolete document, project or iteration. This fix in combination with the fix for Bug#1000196 should not let this happen any longer. And all copied results should come from non-obsolete entities (project, version or document) and should an Approved or Reviewed state.
Comment 3 Damian Jansen 2013-09-10 00:23:42 UTC 
There is a significant number of paths and possibilities that need to be tested in regards to copytrans - however the above appears to be fixed.
Comment 4 Sean Flanigan 2013-11-27 03:16:21 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.
Comment 5 Sean Flanigan 2013-11-27 03:17:19 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.
Comment 6 Sean Flanigan 2013-11-27 03:19:45 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.
Comment 7 Sean Flanigan 2013-11-27 03:25:42 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.
Comment 8 Sean Flanigan 2013-11-27 03:34:35 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.
Comment 9 Sean Flanigan 2013-11-27 03:36:43 UTC 
Closing VERIFIED bugs for Zanata versions <= 3.1.