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

[Bug 20654] New: Omnibus: Update two-column templates to use Bootstrap grid
by bugzilla-daemon＠bugs.koha-community.org 05 Aug '19

05 Aug '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20654 Bug ID: 20654 Summary: Omnibus: Update two-column templates to use Bootstrap grid 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: 14546 This omnibus bug will cover bugs which update two-column template grid markup from YUI to Bootstrap. Typical markup to be replaced: <div id="doc3" class="yui-t2"> <div id="bd"> <div id="yui-main"> <div class="yui-b">  </div> </div> <div class="yui-b">  </div> </div> </div> Replacement: <div class="main container-fluid"> <div class="row"> <div class="col-sm-10 col-sm-push-2">  </div> <div class="col-sm-2 col-sm-pull-10">  </div> </div> </div> Note that "col-sm-push-2" and "col-sm-pull-10" are the classes that reverse the visible column order in the desktop layout. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client templates responsive -- You are receiving this mail because: You are watching all bug changes.

1 103

[Bug 21181] New: Cancel expired holds cronjob does not cancel holds in transit if ExpireReservesMaxPickUpDelay not set
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '19

29 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21181 Bug ID: 21181 Summary: Cancel expired holds cronjob does not cancel holds in transit if ExpireReservesMaxPickUpDelay not set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Debatable, but that problem as it arose: 1 - Patron places a hold, sets 'not needed after' to July 1 2 - Hold is put in transit 3 - Time passes, it is now July 2 4 - Cancel expired holds cron does not cancel hold - found='W' 5 - Hold arrives at destination on July 3 6 - Hold is trapped, patron is notified -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 15679] New: Reset item level hold back to record level hold without deleting and readding the hold
by bugzilla-daemon＠bugs.koha-community.org 26 Jul '19

26 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15679 Bug ID: 15679 Summary: Reset item level hold back to record level hold without deleting and readding the hold Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: hbraum(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Right now, if a hold is tied to a specific item (for any number of reasons), and it needs to be set back to a title level hold, you have to delete and readd the hold. This is cumbersome enough, but it's even more cumbersome when a record has multiple holds (especially 20+), and the hold has to be replaced and manually back in its original priority order. It would be nice if Koha could allow you to reset a hold back to record level after it's been placed, for all cases, including when it's in transit for a patron. Situations arise where an item arrives damaged or is lost in transit and a new item is needed to fulfill the hold. There should probably be a permission to control access to this proposed functionality, like the existing modify_holds_priority permission. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 20959] New: Style checkin form more like the checkout form, with collapsed settings panel
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '19

25 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20959 Bug ID: 20959 Summary: Style checkin form more like the checkout form, with collapsed settings panel Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 76136 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76136&action=ed… Screenshot of the revised checkin form I think it would be nice to make the checkin page look more like the checkout page, with a collapsed panel where settings like book drop mode can be hidden when not in use. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 16399] New: Renewal information should be logged
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '19

22 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16399 Bug ID: 16399 Summary: Renewal information should be logged Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: misilot(a)fit.edu QA Contact: testopia(a)bugs.koha-community.org Currently cannot * view where (ILS-DI/ Opac / Staff Client) * Who Student/Staff member * When an item was renewed. The only thing tracked is in the issues / old_issues table that an item was renewed on a specific date (no time given) and the total number of renewals. No information is logged as described above. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 15814] New: Templates for MARC modification: Edit action does not work.
by bugzilla-daemon＠bugs.koha-community.org 19 Jul '19

19 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15814 Bug ID: 15814 Summary: Templates for MARC modification: Edit action does not work. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org There is an edit button in the tool for MARC template modification for every action of a template. Expected: click edit for an action, get a form populated with the related values. Actual result: page is scrolled to "Add new action", fields are empty. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 18847] New: Add "Save and continue" option to notice editing
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '19

08 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18847 Bug ID: 18847 Summary: Add "Save and continue" option to notice editing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Notices Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org I find myself doing a lot of tweaking when getting HTML notices set up, so I think it would be helpful to have a "Save and continue editing" option. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 16232] New: Edit as new (duplicate) doesn't work correctly with Rancor
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '19

04 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16232 Bug ID: 16232 Summary: Edit as new (duplicate) doesn't work correctly with Rancor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: jweaver(a)bywatersolutions.com Reporter: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Marked as bug because the behavior is confusing (shows empty record but saves over old record). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 20655] New: Z3950 Authorities search is unordered
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '19

04 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20655 Bug ID: 20655 Summary: Z3950 Authorities search is unordered Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Try doing simple search for a new authority from Z39, say Keyword (any): hilton Each page of results is sorted by heading, but going to next page leads to a new sorted list. The results should be sorted overall as biblio results are. I suspect some difficulty is finding the right sort across results, but something like below seems to work in yaz-client: find @or @attr 1=1002 hilton @attr 7=1 @attr 1=1002 0 if I run that on a more generic search though: find @or @attr 1=21 cats @attr 7=1 @attr 1=1002 0 I seem to break the connection -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 20514] New: Searching for a patron using the search field (street address) returns no results if inputting a address stored in multiple db fields
by bugzilla-daemon＠bugs.koha-community.org 02 Jul '19

02 Jul '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20514 Bug ID: 20514 Summary: Searching for a patron using the search field (street address) returns no results if inputting a address stored in multiple db fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P4 Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If inputting a street address of street number and street name which are stored in different db fields (e.g. 'streetnumber' and 'address') this does not return patron results. If however the street number and name are stored in the same db field then results are returned for your search query. At present the only way to search with the search field of address is to either enter ONLY a streetnumber OR a street name unless they are both stored in the same db field. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12