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

[Bug 21737] New: 18.05 manual needs documentation on Grouping of Libraries
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '19

24 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21737 Bug ID: 21737 Summary: 18.05 manual needs documentation on Grouping of Libraries Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This has changed in the Koha version of 18.05. There is documentation needed on this for the new 18.05 manual. This is the bug: [15707] Add ability to define hierarchical groups of libraries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20113] New: Show statistic fields on spend and ordered reports
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '19

23 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20113 Bug ID: 20113 Summary: Show statistic fields on spend and ordered reports 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the acquisitions start page the amounts ordered and spent for each fund are linked to a list of the connected orders. It would be nice if this list also displayed the statistics1 and statistics2 values from the order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 20664] New: Optimize retrieval of biblio and item data
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20664 Bug ID: 20664 Summary: Optimize retrieval of biblio and item data 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: ere.maijala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org There are several inefficiencies in the current process of retrieving biblios and embedding items in the MARC data. These affect especially batch processes such as exporting of records and the OAI-PMH provider. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 21028] New: www/history.t is failing on jenkins for Ubuntu 18.04
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21028 Bug ID: 21028 Summary: www/history.t is failing on jenkins for Ubuntu 18.04 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(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com, mirko(a)abunchofthings.net, nick(a)bywatersolutions.com, tomascohen(a)gmail.com t/db_dependent/www/history.t is failing with the following error on Ubuntu 18.04 (at least with the image from koha-testing-docker): koha_1 | # Failed test 'Cyrillic characters with umlauts show correctly on the history page.' koha_1 | # at t/db_dependent/www/history.t line 68. It is *not* an encoding issue, the problem is that history.txt is not found: Could not read the history.txt file. Please make sure <docdir> is correctly defined in koha-conf.xml. >From koha-conf.xml: <docdir>/usr/share/doc/koha-common</docdir> Indeed this location does not contain history.txt: root@95f30c756223:/kohadevbox/koha# ls /usr/share/doc/koha-common changelog.Debian.gz copyright I have no idea if it is a koha issue, a packaging issue, or a koha-testing issue. Does anyone has an idea? https://jenkins.koha-community.org/job/Koha_18.05_U18/14/consoleFull -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 18549] New: There should be a warning that logging out of Koha will leave browser session logged in to OAuth
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '19

22 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18549 Bug ID: 18549 Summary: There should be a warning that logging out of Koha will leave browser session logged in to OAuth Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org >From bug 16892 Nick: For CAS we have casLogout - can we have something similar here? I think disconcerting if a patron signs in via google, signs out of Koha and walks away leaving their google auth intact unintentionally Mark: This is the problem. If you have multiple tabs, let's say gmail in one, and Koha in the other. If Koha does a forced logout, then your gmail tab will be affected. This is the problem that is widely known. I was thinking of actually doing another bug to drop-down choose what kind of log out. Martin: A federated logout is actually pretty rare in my experience, though it is possible. As you say Mark, it 'feels' strange to the user that logging out of seemingly unrelated apps can have the knock on effect of logging out apps in other tabs that happen to share an aouth2 openid connect identity provider. On a related note, I'm not sure I saw any code out end to support such a federated logout triggered by another service in our end either... but perhaps I missed it ;) Nick: Perhaps if OAuth is activated just a note added that when you log out of Koha you may still be logged in via google? I agree a user with many tabs open may not expect this, but a patron using a shared machine in the library who signs in to place a hold or renew may never visit their email or expect that they have signed in to that. I think a pop-up when logging out to say "Hey, you are logged in to google, and they know lots of stuff about you" wouldn't hurt, who can say if it would help :-) Mark: Perhaps this type of discussion should happen on another bug report, as this bug has nothing to do with logging out. :) Also, yes, some sort of warning should be displayed, somewhere, somehow. Nick: It can happen here now :-) -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 18710] New: Wrong subfield modified in batch item modification
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18710 Bug ID: 18710 Summary: Wrong subfield modified in batch item modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In Tools > Batch item modification, one can modify or delete a subfield. When deleting a subfield et modifying another, the wrong subfield gets modified. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 21058] New: Missing class for results_summary spans
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21058 Bug ID: 21058 Summary: Missing class for results_summary spans Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: david.bourgault(a)inlibro.com Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Some results_summary spans have other CSS class which can be annoying when doing CSS customization. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 21892] New: Robin Sheat is not a typo
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '19

17 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21892 Bug ID: 21892 Summary: Robin Sheat is not a typo Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: QA tools Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: mtompset(a)hotmail.com While testing a bug, I changed a file with "Robin Sheat" in the comments to a .pl file, and the qa test tools flagged Sheat as a typo. It is unlikely that Sheat as a typo will be used in general comments, so the proposal is to ignore Sheat in the codespell call. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 21798] New: We need t::lib::gimme_a_biblio
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '19

16 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21798 Bug ID: 21798 Summary: We need t::lib::gimme_a_biblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 69

[Bug 20216] New: Editing itemtypes does not pull existing values correctly
by bugzilla-daemon＠bugs.koha-community.org 11 Oct '19

11 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20216 Bug ID: 20216 Summary: Editing itemtypes does not pull existing values correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com To recreate: 1 - Edit an item type, define a replacement cost,processing fee, and remote image url 2 - Save the item type 3 - Values are correct in list 4 - Edit again 5 - note values in fields are not populated 6 - Save itemtype, values are lost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23