- Koha-bugs - lists.koha-community.org

[Bug 26923] New: Batch modification for Reports
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26923 Bug ID: 26923 Summary: Batch modification for Reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org It would be useful to update some datas for several reports at a time when selecting them. For more security, only the following fields could be updatde : - group - sub-group - public - Cache expiry -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 33062] New: Report subgroup should be copied when duplicating a report
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33062 Bug ID: 33062 Summary: Report subgroup should be copied when duplicating a report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org When one duplicates a report that's in a group, the new report defaults to going into the same group as the original. But if the original report also has a subgroup that is not passed on to the duplicate. A duplicated report should default to the same group *and* subgroup as its original. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15528] Updating the authorised value for a report subgroup removes the previous value assigned from all report
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15528 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33067] New: Move filters above navigation for subscription search
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33067 Bug ID: 33067 Summary: Move filters above navigation for subscription search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We do have the filters above navigation for tags, suggestions, invoices etc. it makes it more consistent and better usability to have them before the navigation in the left sidebar. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 8328] Max checkouts per time period
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8328 Daniel Gaghan <daniel.gaghan(a)pueblolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.gaghan@pueblolibrary | |.org --- Comment #3 from Daniel Gaghan <daniel.gaghan(a)pueblolibrary.org> --- +1 to this. We would like the option of having a max number of check-outs per day, with a total number of checkouts at a time. So the rules would look something like this. 5 max checkouts per day, 50 total checkouts at a time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 33079] New: Misaligned field in the duplicate order form
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33079 Bug ID: 33079 Summary: Misaligned field in the duplicate order form Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The Statistic 1 field is misaligned in the duplicate order form (acqui/duplicate_orders). To get there : 1. Make sure you have budgets, funds and vendors 2. In Acquisitions, search for a vendor 3. Create a basket 4. Add an order to that basket (Order from new (empty) record is easiest) 5. Add to the basket again, choosing the "From existing orders (copy)" option 6. Search for you previous order 7. Check the order and click Next --> Statistics 1 field is misaligned -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 21263] New: Pickup library not set correctly when using Default holds policy by item type
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21263 Bug ID: 21263 Summary: Pickup library not set correctly when using Default holds policy by item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Not sure if this is a bug or just me misunderstanding the options - Make sure OPACAllowUserToChooseBranch is set to don't allow - Make sure you have two branches A and B - Have one item whose homebranch is B - Have one user whose homebranch is A - Make sure the circulation rules allow the user to reserve the item's item type 1. Go to Administration > Circulation and fines rules 2. Create a Default holds policy by item type for that item type - Item type = item's item type - Hold policy = From any library - Hold pickup library branch = item's home library - Return policy = item returns home 3. Go to the OPAC and log in with the user's credentials 4. Search for the item 5. Click on "Place hold" 6. Confirm hold 7. In the user's file on the OPAC and check the reservation's pickup library What I understand : - Hold policy = From any library: Users from any library can reserve this item type - Hold pickup library branch = item's home library: the pickup library must be the item's homebranch (in this case, B) - Return policy = item returns home: upon return, the items is transferred to its homebranch Therefore, the pickup library in the case above should be B, but it is automatically set to A. P.S. note that I have item-level_itypes set to specific item, and Item level holds set to don't allow. I feel like in this case it should maybe fall back to the record-level item type? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 6796] Overnight checkouts taking into account opening and closing hours
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6796 Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #27 from Emily Lamancusa <emily.lamancusa(a)montgomerycountymd.gov> --- Thanks for the follow-up Aleisha! Unfortunately, I'm still getting some errors when trying to edit a library (testing on KTD). When editing an existing library, upon saving: "An error occurred when updating this library. Perhaps it already exists." When creating a new library, upon saving: "An error occurred when adding this library. The branchcode might already exist." The above two errors occurred consistently regardless of which (if any) fields I edited or what values I entered in those fields. --- It's also failing tests: # Failed test 'Loan period was shortened (but considers the holiday) because ConsiderLibraryHoursWhenIssuing is set to close time' # at t/db_dependent/Circulation/CalcDateDue.t line 413. # got: '2023-02-27T20:35:41' # expected: '2023-03-01T20:35:41' # Failed test 'Loan period was extended (but considers the holiday) because ConsiderLibraryHoursWhenIssuing is set to open time' # at t/db_dependent/Circulation/CalcDateDue.t line 420. # got: '2023-02-28T14:35:41' # expected: '2023-03-01T14:35:41' -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 32915] New: Applying framework defaults
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32915 Bug ID: 32915 Summary: Applying framework defaults Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I am not a cataloger by any means. In my interactions with catalogers, I have come to discover several recent changes occurring with frameworks and defaults. While I don't think we want defaults applying every time you edit a record, there may be times when you want to reset or reapply certain defaults from the framework. Would it be helpful to maybe have a button or batch edit process where you can specify that you would like to reapply defaults, and then pick the ones you want from what the framework applies? Or does this already happen somewhere and I just don't know about it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26965] New: streetnumber field not shown in table when searching by partial patron data
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26965 Bug ID: 26965 Summary: streetnumber field not shown in table when searching by partial patron data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The Patron selection table on circulation.pl displays the patron address, but does not include the streetnumber field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12