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

[Bug 30661] New: Able to update more hold parameters via REST API
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30661 Bug ID: 30661 Summary: Able to update more hold parameters via REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi CC: tomascohen(a)gmail.com If the holds edit endpoint is wanted to use more effectively then it needs more parameters than priority, pickup_library and suspend_until. Is there a plan for PUT action since it has acted as PATCH and is now deprecated? There definitely should be also a real PUT endpoint as documented here https://wiki.koha-community.org/wiki/Holds_endpoint_RFC, now the situation is quite misleading. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 19316] New: Items should have sort1 and sort2 fields
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19316 Bug ID: 19316 Summary: Items should have sort1 and sort2 fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Librarians love data, like for real, they can't get enough. We often find that libraries want extra information in their items table, things that don't fit or don't belong in any of the existing columns. Borrowers have sort1 and sort2 for this kind of information - we should add analogous fields to the items table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 31304] New: Add ability to customise availability searching
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31304 Bug ID: 31304 Summary: Add ability to customise availability searching 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently in Zebra 'limit to available' means: ## 'available' is defined as (items.onloan is NULL) and (items.itemlost = 0) Bug 25375 proposed for ES a slightly wider net: 783 onloan => undef, 784 notforloan => 0, 785 withdrawn => 0, 786 itemlost => 0, 787 damaged => 0 We should have a configuration for this, a way to allow libraries to decide which statuses are available/unavailable -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 27973] New: Limit to currently available items should have an option to filter out notforloan statuses
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27973 Bug ID: 27973 Summary: Limit to currently available items should have an option to filter out notforloan statuses 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Many libraries find it problematic that the 'Limit to currently available' does not filter out notforloan statuses (example: ordered). It would be handy if there was a system preference that allowed librarians to choose which notforloan statuses could be filtered out. to recreate one potential problem: -do an OPAC search that includes some items with a notforloan of -1 (ordered) -click 'Limit to currently available items' -the ORDERED items remain this can be frustrating for a patron who could reasonably assume that after clicking the 'Limit to currently available' filter they would be looking only at items that are currently available to them to checkout -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 27340] New: We should introduce Koha::PickupLocation(s)
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27340 Bug ID: 27340 Summary: We should introduce Koha::PickupLocation(s) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Looking at the codebase, a pickup location is a combination of a branch/library, and now also a 'desk'. So it would make sense to have a special class for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 26915] New: Koha explodes when writing off a fee with FinePaymentAutoPopup
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '24

21 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26915 Bug ID: 26915 Summary: Koha explodes when writing off a fee with FinePaymentAutoPopup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org - To test activate FinePaymentAutoPopup - Create a manual fee - Write it off using the write off button on the account line (not below table) - Experience error on saving the writeoff http://localhost:8081/cgi-bin/koha/members/printfeercpt.pl?action=print&acc… Can't call method "unblessed" on an undefined value at /home/vagrant/kohaclone/members/printfeercpt.pl line 64 This problem was first found in 20.05.03 so affects stable releases as well! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 23264] New: OPAC elements with class="dropdown" include incomplete WAI-ARIA Menu
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23264 Bug ID: 23264 Summary: OPAC elements with class="dropdown" include incomplete WAI-ARIA Menu Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: brian(a)mcneil.ly QA Contact: testopia(a)bugs.koha-community.org Details: Buttons that spawn items with role="menu" must indicate this fact with aria-haspopup="menu", and an aria-controls attribute referencing the id value for the element with role="menu". On expansion, focus should move to the first menu item, and focus should be tracked with either a roving tabindex attribute (so one menu item is always focusable) or tracked with an aria-activedescendant attribute on the element with role="menu". aria-expanded can be used to indicate the state of the button and its attached menu (e.g. expanded or collapsed). This paradigm may apply to over OPAC menus, such as the Lists Menu on the homepage. Steps to Reproduce: 1. Navigate to the element with id="langmenu" 2. Verify this item does not have an aria-haspopup attribute 3. Activate the element, verify a menu appears 4. Verify this content contains an element with role="menu" 5. Verify focus has not moved to the first menuitem beneath the menu 6. Use the arrow keys to adjust content within the menu 7. Verify tabindex attributes are not adjusted and aria-activedescendant is not set on the element with role="menu" Actual Results: Screen readers and other assistive technologies may be unable to interact with content as intended if ARIA controls are not coded to spec. Expected Results: The above listed attributes are added to the button item and element with role="menu". An example of a fully implemented button spawning an element with role="menu" (in this case using aria-activedescendant) can be found at: https://www.w3.org/TR/wai-aria-practices/examples/menu-button/menu-button-a… -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 26813] New: Accessibility: Review labels of page elements
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26813 Bug ID: 26813 Summary: Accessibility: Review labels of page elements Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kathryn(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some page elements are not consistently labelled. Tested this on the staff interface home page only. Would be great to learn the best way to label page elements, make those changes, and test with a screen reader. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25153] New: Accessibility: 1.3.1 Info and Relationships
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25153 Bug ID: 25153 Summary: Accessibility: 1.3.1 Info and Relationships 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 CC: oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Blocks: 23003 There are a few cases where we are not adhering to the 'Headings to Introduce content' guidelines for a A accessibility rating. Headings should be used to introduce the content on all pages, this bug serves as a collector bug for cases where this guideline is not being adhered to. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23003 [Bug 23003] Accessibility improvements -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 26811] New: Accessibility: Improve staff client usability for non-mouse users by changing order of page elements
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '24

19 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26811 Bug ID: 26811 Summary: Accessibility: Improve staff client usability for non-mouse users by changing order of page elements Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: kathryn(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The order of page elements could be improved to enhance the user experience for any user that does not use a mouse and instead tabs through, e.g. screen-reader users or those who prefer to only use the keyboard. To reproduce: When on the staff interface home page, try tabbing through the page elements. Notice the order you go through the elements. (I will open other bugs to address the highlighting of elements, and labels). Currently the first tab goes to the submit button, then back to the check out tab under the search box, then through everything in the left hand column. Suggested order: the next elements to tab across after submit and Check out are the Checkin, Renew, Search Patrons, Search the catalog (all the items across the tabs under the search box), then to the top News block (in case libraries use this for urgent announcements?), back to the modules, then on to the other things down the left hand navigation. Open to other input on the order or things. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3