Bug 1024623 - Context Statistics on filtered documents should show statistics of filtered results
Summary: Context Statistics on filtered documents should show statistics of filtered r...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Usability
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Alex Eng
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-30 06:19 UTC by Ding-Yi Chen
Modified: 2015-07-31 01:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-31 01:22:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Ding-Yi Chen 2013-10-30 06:19:12 UTC
Description of problem:
If filter string is embedding in URL, the context statistics is computed with filtered results.

However, if filter string is typed in document filter field, the context statistics is computed with all documents.

This may confuses users, as the other parts appear exactly the same. 


Version-Release number of selected component (if applicable):
Zanata version 3.0.3 (20130919-2218)


How reproducible:
Always

Steps to Reproduce:
1. Go to https://translate.jboss.org/webtrans/translate?project=jboss_as&iteration=7.1.x&localeId=de&locale=en#filter:App
2. Hover on the context statistics, total words are 239.
3. Clear the document filter field
4. Filter with the string "App"
5. Hover on the context statistics.

Actual results:
Total words are "57439"

Expected results:
Total words are "239"


Additional info:

Comment 1 Alex Eng 2014-05-28 01:10:51 UTC
The initial idea of that statistic is the overall stats for this doc. If we gonna change it to context based, i.e filter, we might do that same in the editor as well. Any suggestions?

Comment 2 Zanata Migrator 2015-07-31 01:22:00 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-460


Note You need to log in before you can comment on or make changes to this bug.