Bug 1018635 - Unexpected behaviour of hours remaining value on filtering
Summary: Unexpected behaviour of hours remaining value on filtering
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-Logic
Version: 3.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Alex Eng
QA Contact: Damian Jansen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 02:06 UTC by Damian Jansen
Modified: 2013-11-27 03:31 UTC (History)
2 users (show)

Fixed In Version:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-27 03:31:17 UTC
Embargoed:

Attachments (Terms of Use)
tmx, po and pot files for project (16.63 KB, application/x-gzip)
2013-10-14 02:06 UTC, Damian Jansen 		no flags Details
View All

Description Damian Jansen 2013-10-14 02:06:39 UTC 
Created attachment 811838 [details]
tmx, po and pot files for project

Description of problem:
In the attached example project, if a user filters the Pl documents list with "About_" (to show only About_Fedora) the hours remaining climbs from 1.4 to 1.5.

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

How reproducible:
Easy always

Steps to Reproduce:
1. Create a project with the files attached
2. Go to about-fedora master
3. Select pl
4. Type About_ in the top left search bar
5. Press Enter

Actual results:
About_Fedora changes from 1.4 hours to 1.5

Expected results:
Should remain at 1.4

Additional info:
Comment 1 Damian Jansen 2013-10-14 02:07:39 UTC 
The easier way to create this is to run the functional-test module with cargo and execute the "Experiment Test" testcase. Then perform the manual steps.
Comment 2 Alex Eng 2013-10-15 05:07:30 UTC 
Fixed in 3.1.1-SNAPSHOT, 
https://github.com/zanata/zanata-server/pull/226
Comment 3 Damian Jansen 2013-10-16 04:25:23 UTC 
Tested at 00c4e17487d7f201bebbc392f2a34fccf108c909
Comment 4 Sean Flanigan 2013-11-27 03:31:17 UTC 
Closing VERIFIED bugs which predate Zanata 3.1.2.
Note You need to log in before you can comment on or make changes to this bug.