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

[Bug 28982] New: Use Flatpickr on onboarding pages
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '22

10 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28982 Bug ID: 28982 Summary: Use Flatpickr on onboarding pages 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 Depends on: 28937, 28376 There is one datepicker instance in the onboarding templates which should be replaced with Flatpickr. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28376 [Bug 28376] Replace obsolete jquery-ui-timepicker-addon https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28937 [Bug 28937] Use Flatpickr on circulation and patron pages -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 29661] New: PreFillItem should not apply to duplicated items
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '22

09 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29661 Bug ID: 29661 Summary: PreFillItem should not apply to duplicated items Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In 21.05.07, the PreFillItem syspref is applied when duplicating an item. This was not the case in previous versions of Koha and is not the case on master. To recreate (on 21.05): - set PrefillItem to "the new item is prefilled ..." - set SubfieldsToUseWhenPrefill to 3 so that the Materials Specified value is prefilled - create an item that has a Materials Specified note - confirm that when the Add Item page reloads after creating your item, the Materials Specified note is prefilled as expected - find an item without a Materials Specified value, duplicate it - confirm your duplicate item's Materials Specified is prefilled with the value from your first item, when it should be null like your second item -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29763] New: Patron information - terminology; borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 09 Jan '22

09 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29763 Bug ID: 29763 Summary: Patron information - terminology; borrowernumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On the patron details page the 'Borrowernumber' is shown on the top left patron information section. 'borrowernumber' is used as part of the query/URL and is the assigned number given to a patron in the database. It is also used in other areas of the staff interface, such as the patron batch modification tool (Tools > Patrons > Patron batch modification) - see the tab 'By borrowernumber', where you can enter a list of 'borrowernumbers' to modify. Should this be renamed to something more human friendly rather than what the system uses to identify this field? Such as 'Patron number'. Our terminology list says we should use patron, rather than member or borrower: https://wiki.koha-community.org/wiki/Terminology -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29237] New: When deleting funds from an inactive budget, the results page returns to a different budget
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29237 Bug ID: 29237 Summary: When deleting funds from an inactive budget, the results page returns to a different budget Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: valerie(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In Administration/Budgets, I am in the "inactive budgets" tab, deleting funds under a specific budget. (In this instance, budget period #29.) When I select "delete" for the fund, it opens a new page to verify that I want to delete this budget. After it completes the deletion, it goes to a different budget, an active budget. (In this case, budget period #30). I confirmed that the fund was deleted as expected from the inactive budget, but with the page going to a different budget when complete, a user could easily delete something unintended. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29559] New: Update creates "unexpected type" entries for standard codes in debit and credit types
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29559 Bug ID: 29559 Summary: Update creates "unexpected type" entries for standard codes in debit and credit types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 CC: martin.renvoize(a)ptfs-europe.com After an update from 18.11 to 20.11.11 we notice that there are a lot of "Unexpected type found during upgrade (Voided)" in the patron accounts. It looks like 19.12.00.027 / Bug 24532 and maybe others are related to this. Following entries have been added: select * from account_credit_types; LOST select * from account_debit_types; Pay W It could be related to voiding entries, but I am not fully understanding the issue yet. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 28812] New: Authority tag editor only copy $a
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28812 Bug ID: 28812 Summary: Authority tag editor only copy $a Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Depends on: 7882 Steps to reproduce: 1- Create a notice with a 700$a and 700$d 2- Click on Tag Editor 3- Only 700$a is copied Expect result: same as 19.11 all other subfields should be copied. There's now one more level in HTML tree and koha-tmpl/intranet-tmpl/prog/js/cataloging.js:openAuth() selects the wrong node. To check: still working in authorities/authorities.pl ==== diff --git a/koha-tmpl/intranet-tmpl/prog/js/cataloging.js b/koha-tmpl/intranet-tmpl/prog/js/cataloging.js index f126c86de2..35cbe499ae 100644 --- a/koha-tmpl/intranet-tmpl/prog/js/cataloging.js +++ b/koha-tmpl/intranet-tmpl/prog/js/cataloging.js @@ -43,8 +43,8 @@ function openAuth(tagsubfieldid,authtype,source) { var elementsubfcode=getSubfieldCode(element.name); var mainmainstring=element.value; var mainstring = new Array(); - var inputs = element.parentNode.parentNode.getElementsByTagName("input"); + var inputs = element.parentNode.parentNode.parentNode.getElementsByTagName("input"); for (var myindex =0; myindex<inputs.length;myindex++){ if (inputs[myindex].name && inputs[myindex].name.match(tagsubfield)){ var subfieldcode=getSubfieldCode(inputs[myindex].name); Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7882 [Bug 7882] Add ability to move and reorder fields and subfields in MARC editor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 28693] New: Main heading box not populated in search authorities from bibliographic record
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28693 Bug ID: 28693 Summary: Main heading box not populated in search authorities from bibliographic record Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Workflow (on 20.11.05) 1. Add 610 values of a Great Britain. b Parliament x Rules and practice in order to edit catalogue record 2. Click gadget for authority search 3. Observe only "search main heading ($a only):" box is populated (Great Britain) but not "Search main heading:" box (which should contain Parliament Rules and practice) This means you get loads of results when you click search as it just searches for Great Britain. This makes it difficult to find navigate to the authority record you need. NB/ In 19.11.04 both boxes are populated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 29751] New: [DOCS] Document how linking from Koha to the manual works
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29751 Bug ID: 29751 Summary: [DOCS] Document how linking from Koha to the manual works Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Documentation Assignee: david(a)davidnind.com Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org >From the 16 December 2021 documentation meeting: "document how the linking from Koha to the manual works". See: http://irc.koha-community.org/koha/2021-12-16#i_2394778 -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 27033] New: Add plugin hook to add a big link in staff home page
by bugzilla-daemon＠bugs.koha-community.org 08 Jan '22

08 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27033 Bug ID: 27033 Summary: Add plugin hook to add a big link in staff home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In staff home page we have some big links : Circulation, Patrons ... Add plugin hook to add such a link. Defined by a CSS class, an URL, a Font Awesome icon and a content. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 27527] New: Plugin hooks to create additional contents
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '22

07 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27527 Bug ID: 27527 Summary: Plugin hooks to create additional contents Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org It would be useful to let plugin create contents that we will integrate into Koha. The idea is to have a hook (on the main page for instance) that will retrieve a list of URL that will be displayed at the end of the page. The URL could be: - A link to an external website - A link to an existing view of Koha - A link to a specific content The specific content would be returned by the plugin and displayed nicely integrated into Koha. -- You are receiving this mail because: You are watching all bug changes.

1 10