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

[Bug 27025] New: jQuery testing with specific user
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27025 Bug ID: 27025 Summary: jQuery testing with specific user Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 have been able to apply jQuery that only applies to a specific user that is logged in. I would propose that Koha would use similar techniques and create a jQuery test field that only applies to Koha if a specific user is logged in. This would be completely separate from the usual jQuery that is applied, but applied along with the usual jQuery, for testing purposes. It would have no affect on other users in a production environment, but allow for admin to test new jQuery before applying to the regular jQuery. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 16486] New: Display the TIME a fine was collected/written off
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16486 Bug ID: 16486 Summary: Display the TIME a fine was collected/written off Change sponsored?: --- Product: Koha Version: 3.20 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In many cases it would be very useful to be able to know the time a fine was collected/written off (in addition to the date). So ideally, the TIME could be shown next to the date in the Fines->Account tab. (This would make sense in almost all cases except maybe in Accruing fines). Alternatively, a text could be added to the description column. For example, "Payment, thanks" could become "Payment on 15/09/2015 14:30, thanks", "Writeoff" could become "Written off on 15/09/2015 14:30", etc -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 93

[Bug 27246] New: Remove apache only code from C4::Context BEGIN
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27246 Bug ID: 27246 Summary: Remove apache only code from C4::Context BEGIN Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 27797] New: Make POST /holds use the stashed koha.overrides
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27797 Bug ID: 27797 Summary: Make POST /holds use the stashed koha.overrides 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: tomascohen(a)gmail.com Bug 26181 introduced a way to override behavior through a new header, x-koha-override. It was being discussed outside BZ, and it got pushed. The agreement Martin and I reached while it was getting through QA was that we could take the chance and do not override a specific syspref, but use codes to designate what behavior would be overriden. And specifically about 26181, we decided 'any' was better than explicitly putting the syspref on the header. This bug will use bug 27760 to change how it is done, and will rename the value to be passed on the header, while retaining the current behavior, of failing even if Can*BeReserved fails even if AllowHoldPolicyOverride is set, on the API, unless the header is passed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 27760] New: Add handling for x-koha-override
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27760 Bug ID: 27760 Summary: Add handling for x-koha-override 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: tomascohen(a)gmail.com On the development of bug 26181, Martin and I were discussing a more generic approach, when suddenly the bug went SO => QA => Pushed to master => Backported to all stable branches :-D. My fault for not setting it 'In discussion'. We should use a follow-up to adjust the pushed implementation in line with bug 26181 comment 9. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 26645] New: t/Koha/Script.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 11 May '21

11 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26645 Bug ID: 26645 Summary: t/Koha/Script.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(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 25551 First time we see this one I think Koha_Master_D11 #103 14:41:47 koha_1 | # Failed test 'Exception found' 14:41:47 koha_1 | # at t/Koha/Script.t line 67. 14:41:47 koha_1 | # '' 14:41:47 koha_1 | # doesn't match '(?^u:Unable to acquire the lock.*)' 14:41:50 koha_1 | # Looks like you failed 1 test of 3. 14:41:50 koha_1 | 14:41:50 koha_1 | # Failed test 'lock_exec() tests' 14:41:50 koha_1 | # at t/Koha/Script.t line 85. 14:41:50 koha_1 | # Looks like you failed 1 test of 4. 14:41:50 koha_1 | [12:41:50] t/Koha/Script.t Referenced Bugs: 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 4

[Bug 25557] New: Column config table in Acquisitions Order Does not Match the Acq table in Baskets
by bugzilla-daemon＠bugs.koha-community.org 10 May '21

10 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25557 Bug ID: 25557 Summary: Column config table in Acquisitions Order Does not Match the Acq table in Baskets Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Tools Assignee: lucas(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The actual way that the Acq table appears in the basket view (basket.pl), 1.Basket # 2. Order information 3. RRP Tax Exc 4. Actual Cost Exc 5. Budgeted Cost Tax Exc 6. RRP Tax Included 7. Actual Cost Tax Inc 8. Budgeted Cost Tax Inc 9. Replacement Price 10. Quantity But in the column config table 1.Basket # 2. Order Info 3. RRP tax Exc 4. Ecost Exc (Actual Exc) 5. RRP tax Included 6. Ecost Tax Included (Actual Inc) 7. Replacement Prie 8. Quantity 9. Total Tax Excluded 10. Total Tax Included We will need to change the column configuration to match the table so it is easy to hide the correct columns. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 26139] New: 'Place Hold' button isn't hidden in all biblio views if there's no items available for loan.
by bugzilla-daemon＠bugs.koha-community.org 10 May '21

10 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26139 Bug ID: 26139 Summary: 'Place Hold' button isn't hidden in all biblio views if there's no items available for loan. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl At cgi-bin/koha/catalogue/detail.pl 'Place Hold' button is not hidden in : ISBD an Items view -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 24492] New: Add a 'branch cashup' workflow to the point of sale system
by bugzilla-daemon＠bugs.koha-community.org 10 May '21

10 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24492 Bug ID: 24492 Summary: Add a 'branch cashup' workflow to the point of sale system Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Bug 23355 adds a cashup workflow for individual cash registers, but it would be nice to have a branch summary and cashup option too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 22371] New: MARC bibliographic framework plugin to generate Cutter-Sanborn
by bugzilla-daemon＠bugs.koha-community.org 09 May '21

09 May '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22371 Bug ID: 22371 Summary: MARC bibliographic framework plugin to generate Cutter-Sanborn Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: italo.barbosa.brasileiro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- The plugin (.pl) generates the Cutter-Sanborn code, and will be added to the list of plugins intended for the fields in MARC bibliographic frameworks. To use the plugin, it is necessary to associate it with the Cutter field in the framework. By clicking on the Cutter field, the plugin generates the Cutter code, from the values entered in the fields 100$a (Personal name), 110$a (Corporate name) and/or 245$a (Title statement). An initial version of the plugin was created, which operates as follows: 1) Use the field 100$a to generate the Cutter, and adds the first letter of the title (245$a) to the end of the Cutter code; 2) If field 100$a is not filled, use field 110$a and add the first letter of the title (245$a) to the end of the Cutter code; 3) If none of the fields 100$a or 110$a are filled, the cutter is generated from field 245$a, without adding the first letter of the title to the end of the code. Some observations: - To fill the Cutter, simply click on the field and the cutter is displayed. - If none of the fields are filled, the cutter is not generated. - It is important to fill the indicator 2 of field 245 with the number of characters used by the article preceding the title of the work (if any). The blank spaces also count. If the indicator 2 is not filled, the plugin understands that the value is 0. - For fields with special characters, the following list of characters is currently considered: ãâáàÃÃÂÁÀÉÊéêÍÎíîóõôṌÕÔṌÚÛúûçÇÑñ -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25