Bug 4284 - don't show planning category fields if there were none
Summary: don't show planning category fields if there were none
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: PC All
: P5 - low minor
Assignee: Henri-Damien LAURENT
QA Contact: Bugs List
URL: /cgi-bin/koha/acqui/neworderempty.pl?...
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-26 05:18 UTC by Nicole C. Engard
Modified: 2014-12-07 20:02 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
planning on order (46.85 KB, image/png)
2010-02-26 17:18 UTC, Chris Cormack
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 01:25:22 UTC


---- Reported by nengard@gmail.com 2010-02-26 17:18:57 ----

Created an attachment
planning on order

The planning category fields shouldn't show on the basket if the fund doesn't have any planning categories set for it.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:25 UTC  ---

This bug was previously known as _bug_ 4284 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4284
Imported an attachment (id=1976)

Actual time not defined. Setting to 0.0
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
The original submitter of attachment 1976 [details] is unknown.
   Reassigning to the person who moved it here: chris@bigballofwax.co.nz.

Comment 1 David Cook 2013-02-22 03:50:11 UTC
I think this bug is obsolete at this point, as these "planning value" fields have been changed to "Statistic" fields in Acquisitions. There is no need to connect the planning fields with the planning categories for the fund.

That said, no drop-down menus are being created for these "Statistic" fields when Asort1 and Asort2 are defined in the authorised_value list (compare this behaviour to the BSort1 and BSort2 authorised value categories which populate that Sort1 and Sort2 fields in the add/edit Patron record screen).

Closing this bug and opening a new one for the latter issue.