Bug 7406 - saved reports not showing right number
Summary: saved reports not showing right number
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: 3.6
Hardware: All All
: P5 - low normal
Assignee: Frédéric Demians
QA Contact: Ian Walls
URL:
Keywords:
: 7527 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-01-05 18:28 UTC by Nicole C. Engard
Modified: 2013-12-05 19:59 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Proposed patch (934 bytes, patch)
2012-02-08 18:16 UTC, Frédéric Demians 		Details | Diff | Splinter Review
[SIGNED-OFF] Bug 7406 Fix saved reports display paging inconsistency (1.01 KB, patch)
2012-02-09 13:49 UTC, Owen Leonard 		Details | Diff | Splinter Review
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2012-01-05 18:28:16 UTC 
See here: http://screencast.com/t/Wx7sVgkfb 

When you go to the used saved page it's showing 40 reports but the filter says 20 so that when you changing things by sorting a column it changes to 20 and when you page through things aren't looking right either.  The limit on number of reports should match what is shown on the page.
Comment 1 Frédéric Demians 2012-02-08 18:16:48 UTC Comment hidden (obsolete)
Comment 2 Owen Leonard 2012-02-09 13:49:34 UTC 
Created attachment 7526 [details] [review]
[SIGNED-OFF] Bug 7406 Fix saved reports display paging inconsistency

Signed-off-by: Owen Leonard <oleonard@myacpl.org>
Comment 3 Owen Leonard 2012-02-10 16:30:59 UTC 
*** Bug 7527 has been marked as a duplicate of this bug. ***
Comment 4 Ian Walls 2012-02-16 17:09:51 UTC 
Simple template-only change to default value for page sorter (50 down to 20).  Marking as Passed QA.
Comment 5 Jared Camins-Esakov 2012-05-23 13:01:53 UTC 
This fix was included in the 3.6.x branch prior to 3.6.4.