Hide Forgot
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.
Some unwanted copy trans results were not being filtered out. See: https://github.com/zanata/zanata-server/pull/149
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.
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.
Closing VERIFIED bugs for Zanata versions <= 3.1.