---- Reported by email@example.com 2010-01-19 10:59:46 ----
2 more columns are needed in csv export of overdues :
* item callnumber
* issue date
---- Additional Comments From firstname.lastname@example.org 2010-01-19 13:18:08 ----
first name and last name must be separated in two columns.
---- Additional Comments From email@example.com 2010-02-08 17:40:12 ----
The patches that were sent to firstname.lastname@example.org do not apply against HEAD and never did. Please resubmit.
--- Bug imported by email@example.com 2010-05-21 01:22 UTC ---
This bug was previously known as _bug_ 4051 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=4051
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.
Patches were applied to 3.0.x but never resubmitted for HEAD.
Do we need these for master?
Paul, is this something you think we need in master?
Created attachment 5242 [details] [review]
Yes, I think it's worth having date due (as well as callnumber, was not specified in previous comments) in what is exported in CSV
Created attachment 5243 [details] [review]
oups, typo in comment = it's issuedate and not date_due (that was already here)
(Only the patch comment has been updated)
Comment on attachment 5242 [details] [review]
As far as I can tell, this is obsoleted by Attachment #5243 [details].
itemcallnumber is already included in the CSV export, see:
After applying this patch it is included twice in the SQL query. It only shows up once in the generated CSV, but I'm marking this as failed QA...
Created attachment 6520 [details] [review]
patch adding issuedate
Patch adding the issuedate column only (itemcallnumber being already present).
Created attachment 6556 [details] [review]
Bug 4051: adds issuedate column to overdues export
Signed-off-by: Chris Cormack <firstname.lastname@example.org>
QA comment: small patch, easy to read, passed QA
Patch pushed, please test
chris_n = I think it's an enhancement, and suggest not to backport this bug to 3.6: ppl that have automated scripts with CSV may be confused by their scripts not working anymore. But, as usual, it's up to you