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

[Bug 16126] New: Display base-level amounts on the acquisition module home page
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16126 Bug ID: 16126 Summary: Display base-level amounts on the acquisition module home page 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: francois.charbonnier(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This patch will display on the acquisition module home page the information already displayed on the "manage fund" page (aqbudgets.pl). Currently, Koha display the base-level amounts only. This patch will : 1. rename the column "ordered", "spent" and "available" to "base-level [ordered|spent|available]" 2. add the column "ordered", "spent" and available with the same calculation from the "manage fund" page. TEST PLAN : 1. Go to the Administration module 2. Add a new budget (ie : Budget 2016) 3. Add a fund to this budget (ie : Book) 4. Add a child fund (ie : Adult fiction) You will have this hierarchy : Budget 2016 |____ Book |_____ Adult fiction 5. Go to the Acquisition module 6. Place an order and use the "Adult fiction" budget 7. Go back the Acquisition home page and compare the table with the table from the aqbudgets.pl page (Administration > Budget > Fund) 8. You will see : BEFORE PATCH : the base level amounts only AFTER PATCH : the base level and the total amounts -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 23767] New: Spent and Ordered total values don't include child
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23767 Bug ID: 23767 Summary: Spent and Ordered total values don't include child Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 57

[Bug 16121] New: Reports need a counter of uses, and date of last use
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16121 Bug ID: 16121 Summary: Reports need a counter of uses, and date of last use Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org In an effort to keep reports tidy, it would be helpful if the guided_reports.pl?phase=Use saved, phase=Edit SQL, and phase=Show SQL showed a count of the number of times the report has been run, along with the date it was last run on. This would require two new fields, such as "Use count" and "Last run date". Christopher -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 16109] New: Toolbars wrapping on narrower browsers
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16109 Bug ID: 16109 Summary: Toolbars wrapping on narrower browsers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 49326 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=49326&action=ed… Buttons on members-toolbar.inc wrapping when I make my browser smaller -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 16093] New: Streamline Holds awaiting pickup cancel process
by bugzilla-daemon＠bugs.koha-community.org 09 Sep '23

09 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16093 Bug ID: 16093 Summary: Streamline Holds awaiting pickup cancel process Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 I would like to suggest some improvements to the Holds over tab in the Holds awaiting pickup tables (waitingreserves.pl): In addition to seeing 13838 pushed to master, I would love to see the following: * Checkboxes next to items, along with a Cancel selected button next to the Cancel All button, with a confirmation. * I haven't confirmed, but if the Cancel all button doesn't already have it, it should also have a confirmation. * Preference to print slips on items that are cancelled individually with the Cancel hold and return to button. * Items that have hold requests should indicate that on the button rather than the "return to" information. * Items that have hold requests end up with TWO statuses on them in this process. They end up with a transfer to the owning library and a hold transfer. In cases where there is a hold request on the item, the transfer status should be skipped and the hold request honored, with the appropriate slip. * If the list is sorted by a particular column, the sort should remain intact when the screen refreshes (bug 13838 solves half the battle by keeping you on the same tab). Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34085] New: Remove the use of event attributes from basket groups template
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34085 Bug ID: 34085 Summary: Remove the use of event attributes from basket groups template Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 17858 There are some event attributes in the basket groups template. These should be removed in favor of defining events in JavaScript. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17858 [Bug 17858] [OMNIBUS] Move staff client JavaScript to the footer -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 24860] New: Add ability to place volume level holds
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24860 Bug ID: 24860 Summary: Add ability to place volume level holds 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This feature builds upon bug 24857 and allows placing holds that target a specific volume of a record. It is patterned after the feature that allows limiting hold selection by itemtype ( AllowHoldItemTypeSelection ). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 270

[Bug 34746] New: Branch preferences should not be tied to staff preferences
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34746 Bug ID: 34746 Summary: Branch preferences should not be tied to staff preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 We run a tight ship, and don't create separate accounts for personal library accounts and staff login accounts. That being said, the login for staff is different than patron login, and a staff member's default pickup location is not always the same as the branch they work at. It would be nice if the branch and credentials you use to work as a staff member didn't touch the home branch and credentials used as a library patron in the OPAC. Some possible suggestions would be: * Default branch and credentials for staff login under user permissions * Staff credentials can't be used for OPAC patron logins * OPAC patron logins can't be used for staff logins This would allow an existing patron account to be added and removed as staff, without changing their patron experience or defaults. The only sticky issue would be patron category. How could an account that serves as both patron and staff have both? Could a category be set for the staff side of things, and a separate category be used for the patron side of things? Should there be a setting in system preferences to use the staff category on the account when they are logged in on the staff side, and retain the patron category when not? Am I asking too much of Koha? It has always been a little odd that we use the same patron database for both patron and staff (based on my previous ILS experience), and because of that, it has led us to trying to maintain a single account for a person. If they were separated out as separate databases or tables, rather than blended together, then I wouldn't have so much of a problem having an account in each. A separate staff table would be much nicer for staff management, but might alter things quite a bit in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 34177] New: Call number browser is not opening in new window
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34177 Bug ID: 34177 Summary: Call number browser is not opening in new window 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: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The call number browser is not opening in a new pop-up window as expected. This causes an issue in workflow whenever a library uses it because submitting a search will cause the Koha navbar and header_search to disappear. /cgi-bin/koha/cataloguing/plugin_launcher.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 34682] New: Previously merged patron is showing up in new patron merge
by bugzilla-daemon＠bugs.koha-community.org 08 Sep '23

08 Sep '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34682 Bug ID: 34682 Summary: Previously merged patron is showing up in new patron merge Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Merge two patrons (Patron B into Patron A) 2. Now select patron C & D and start merging them. 3. Patron A (previously merged patron) is showing on the patron-merge-table. If you try merging patron D into patron C it will merge both patron D and A into C. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5