Bug 1086059

Summary: [TM] Newer translation should be in the front for same similarity
Product: [Retired] Zanata Reporter: Yuko Katabami <ykatabam>
Component: Component-LogicAssignee: Damian Jansen <djansen>
Status: CLOSED DUPLICATE QA Contact: Zanata-QA Mailling List <zanata-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3CC: camunoz, dchen, zanata-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-17 02:08:32 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 Yuko Katabami 2014-04-10 03:12:04 UTC 
Description of problem:
Zanata TM currently does not always prioritize the most recent translation.
When you have multiple 100% matches, it often lists older strings or the one has higher counts at the top of TM pane.

Version-Release number of selected component (if applicable): 3.3


How reproducible: not sure


Steps to Reproduce:
1. Open a Zanata project and find a string which has multiple 100% matches
2. Check the information of each entry (last translated date / count)
3. Verify the one placed on the top is the right one or not.

Actual results:
It does not always list the most recent one at the top.

Expected results:
The most recent one should be listed at the top

Additional info:
Pre-discussed with Carlos. This is for preparation for project-wide TM merge feature.
Comment 1 Ding-Yi Chen 2014-04-17 02:08:32 UTC 

*** This bug has been marked as a duplicate of bug 1086459 ***