Bug 7831 - In neworderempty budget drop down budgets should appear in a rational order
Summary: In neworderempty budget drop down budgets should appear in a rational order
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: 3.6
Hardware: All All
: P5 - low minor
Assignee: Colin Campbell
QA Contact: Ian Walls
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 15:01 UTC by Colin Campbell
Modified: 2013-12-05 19:59 UTC (History)
2 users (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 (829 bytes, patch)
2012-03-27 15:13 UTC, Colin Campbell 		Details | Diff | Splinter Review
Bug 7831 : Sort budgets for selection in new order (882 bytes, patch)
2012-04-07 07:24 UTC, Chris Cormack 		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 Colin Campbell 2012-03-27 15:01:31 UTC 
Budgets are listed in the fund selection dropdown in an order which does not make sense for the user, To improve this the budgets array should be sorted bu the visible text field
Comment 1 Colin Campbell 2012-03-27 15:13:05 UTC Comment hidden (obsolete)
Comment 2 Chris Cormack 2012-04-07 07:24:17 UTC 
Created attachment 9001 [details] [review]
Bug 7831 : Sort budgets for selection in new order

The select budget dropdown list should be presented in
an ordered fashion. To achieve this sort the budget array
by the visible text.

Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz>
Comment 3 Chris Cormack 2012-04-07 07:25:06 UTC 
Simple patch, puts the funds into a sane order, signed off
Comment 4 Ian Walls 2012-04-09 17:28:19 UTC 
Simple enough sorting added, makes the budgets quicker to scan with the eye.  Marking Passed QA.
Comment 5 Paul Poulain 2012-04-12 16:26:38 UTC 
Patch pushed, I don't think this is an ENH, it's a minor bugfix (so worth for 3.6)
Comment 6 Jared Camins-Esakov 2012-05-24 00:57:39 UTC 
This patch will be included in 3.6.5.