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

[Bug 32506] New: Prevent creation of same fund code within a single budget
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '25

03 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32506 Bug ID: 32506 Summary: Prevent creation of same fund code within a single budget Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org When adding funds to a single budget, staff should not be able to create two funds using the same fund code. This happened at our library and wasn’t discovered until we had received titles in the two duplicate fund codes. We then had to combine everything into the one fund code. Keeping the fund codes unique would prevent confusion and staff time it took to fix our mistake. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28762] New: Item status shows incorrectly on course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28762 Bug ID: 28762 Summary: Item status shows incorrectly on course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: - create a course in course reserves, add an item to it. - confirm your item shows Available for its status on course-details.pl - edit your item to be withdrawn, lost, damaged, notforloan, and restricted use - reload course-details.pl, confirm it still shows available filed bug 28761 for this on the OPAC. On the OPAC, withdrawn, lost, and damaged *do* update the status. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 140

[Bug 30699] New: Several id idx
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '25

02 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30699 Bug ID: 30699 Summary: Several id idx Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In koha-tmpl/intranet-tmpl/prog/en/includes/search_indexes.inc there is : <select class="advsearch" name="idx" id="idx"> But this include is used several times, so there are several id="idx". We should remove this id. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 30979] New: Add ability for opac users to checkout to themselves
by bugzilla-daemon＠bugs.koha-community.org 30 May '25

30 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30979 Bug ID: 30979 Summary: Add ability for opac users to checkout to themselves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org In some trusted environments libraries would like their users to self-issue without having to use the SCO or SIP checkouts. i.e. once logged in a user should have the ability to check out to themselves much like they already have the option to renew and place holds etc. -- You are receiving this mail because: You are watching all bug changes.

1 187

[Bug 30281] New: Schedule batch patron deletion and anonymization
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30281 Bug ID: 30281 Summary: Schedule batch patron deletion and anonymization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would love to see someone incorporate reoccurring scheduling on this page that didn't require us to setup a cron job on the backend. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27935] New: Allow item search fields to be defined from database fields rather than MARC tags
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27935 Bug ID: 27935 Summary: Allow item search fields to be defined from database fields rather than MARC tags Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The item search fields interface allows one to specify MARC tags to be used as custom search fields. It'd be handy to also have the option of specifying database fields, for the various bib/item values that don't get stored in the MARC. This would be handy for folks who don't or can't use reports and therefore rely on item search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 32268] New: t/db_dependent/XSLT.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32268 Bug ID: 32268 Summary: t/db_dependent/XSLT.t is failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 19532 Blocks: 25551 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19532 [Bug 19532] Recalls for Koha https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25551 [Bug 25551] [OMNIBUS] Some tests are failing randomly -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 32445] New: Status display of 'not for loan' items is broken in OPAC/staff
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32445 Bug ID: 32445 Summary: Status display of 'not for loan' items is broken in OPAC/staff Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org This is a display issue, but marking as major since it affects a basic functionality in the OPAC: 1) Edit any item, item type should be for loan, so not set to reference. 2) Set Not for loan status to "not for loan". 3) Go to the staff detail page: 4) Verify it displays as: Not for loan (Not For Loan) Available The available should not be there! 5) Go to the OPAC detail page: 6) Verifiy the status displays as: Available This should display the not for loan status! -- You are receiving this mail because: You are watching all bug changes.

1 67

[Bug 31147] New: Recalls due date to the minute rather than 23:59
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31147 Bug ID: 31147 Summary: Recalls due date to the minute rather than 23:59 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com I don't know if this is intended behaviour or a bug. When placing a recall, the new due date is exactly now + recall due date interval. Let's say my recall due date interval is 7 and an item is due 2022-08-31 23:59:00. If I place my recall today (2022-07-12) at 16:31:14, the new due date will be 2022-07-19 16:31:14. Like I said, I'm not sure if this is the intended behaviour, but in my very unknowledgable opinion, I find it a bit extreme to ask someone out of the blue to return an item by a certain time (to the second). To test: 1) Turn on recalls 1.1) In Administration > Global system preferences, enable UseRecalls 1.2) Add recalls permissions in your circulation rules 2) Find a record with a checked out item; check the due date for that checked out item, e.g. SELECT date_due FROM issues WHERE itemnumber = XXXX; --> It should be YYYY-MM-DD 23:59:00 3) In the OPAC, log in as a patron 4) Find the same record and place a recall 5) Check the new due date --> It should be today + the number of days you put in recall due date interval in step 1.2 at the exact time you placed the recall -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 32129] New: Use patron categorycode of most relevant recall when checking if item can be a waiting recall
by bugzilla-daemon＠bugs.koha-community.org 29 May '25

29 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32129 Bug ID: 32129 Summary: Use patron categorycode of most relevant recall when checking if item can be a waiting recall Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We check in (return) an item to trigger the recalls process and set it as waiting for the patron who requested the recall. Sometimes the recalls process isn't triggered, and there is no other way to alert the patron that their item is ready for them to pick up if they've recalled it. This is because of more specific circulation rules. When we check if an item can be set as waiting to fill a recall, we do not consider the category code. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20