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

[Bug 18948] New: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18948 Bug ID: 18948 Summary: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This patchset aims to add the ability to leverage the ES alias feature during a reindex - when doing a full reindex or a deletion the indexer will look for an existing index under the alias - if not found it will create a new one, if found it will index into a new index and point the alias there when done and then delete the old index. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 25825] New: Allow Claim Return function to be controlled by permissions
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25825 Bug ID: 25825 Summary: Allow Claim Return function to be controlled by permissions Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be helpful to have a way to control which users are able to initiate and resolve a claim return. Some libraries will only want certain levels of staff to be able to initiate the Claim Return, and likewise, only certain staff should be able to resolve it. Perhaps a permission for each of those functions? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 23898] New: New data to share on HEA
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23898 Bug ID: 23898 Summary: New data to share on HEA 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: paul.poulain(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Some ideas of thing that could be shared on HEA for statistics purposes: - adding some statistics like "intranetuserjs yes/no" => yes if there's something, no if it's empty ? (intranetuserjs, opacuserjs, opac & intranet css, opacheader, opacnav, opacbottom). - For sysprefs *XSLT* => we could send "empty/default/local". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 25384] New: Label maker font list is not configurable
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25384 Bug ID: 25384 Summary: Label maker font list is not configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The label maker font list is hard-coded to 12 arbitrary choices. It would be better if we could configure the font choices in the user interface (since we can already configure the truetype font files in koha-conf.xml). -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 21779] New: Holds history doesn't show where hold placed
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '26

24 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21779 Bug ID: 21779 Summary: Holds history doesn't show where hold placed Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: siobhancottam(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The Holds history tab doesn't show the same information as the modification log e.g. if the reservation was placed in the OPAC or staff client. It is possible to find this information from the log viewer, but not from a patron record modification log as this doesn't show holds at all. This is time-consuming to find the relevant hold if you don't already know the approximate date when the hold was placed. The system log uses the reserve ID as the Object, which is presumably why it doesn't show in the Patron log where their borrowernumber is the Object no. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 27314] New: Update default Elastic mapping
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '26

23 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27314 Bug ID: 27314 Summary: Update default Elastic mapping Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: nick(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com As we've been bringing libraries online with Elastic searching, we've run into a handful of changes to the default mappings. I'm filing this bug to remind us to push some of those back into the community defaults. I'll circle back here with details of changes we've made. Anyone else have changes they'd like to see in the community ES mappings? -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 21592] New: When adding to basket from a file and using MarcFieldsToOrder items are not added to basket if missing funds
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '26

23 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21592 Bug ID: 21592 Summary: When adding to basket from a file and using MarcFieldsToOrder items are not added to basket if missing funds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Test plan: 1 - Edit the MarcItemFieldsToOrder and MarcFieldsToOrder syspref. For example: MarcItemFieldsToOrder homebranch: 975$a holdingbranch: 975$b itype: 975$c nonpublic_note: 975$d public_note: 975$e loc: 975$f ccode: 975$g price: 975$h replacementprice: 975$i itemcallnumber: 975$j notforloan: 975$m uri: 975$n copyno: 975$o MarcFieldsToOrder price: 975$h 2 - Stage your order file from vendor. (Test file : https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=57715 ) 3 - Add to basket from staged file 4 - Values are filled but not budget (ensure you don't have the one in file defined) 5 - Check the box and save 6 - You are returned to empty basket 7 - View the record - items have been created -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 27579] New: Add field for creator to Manage staged MARC records
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '26

18 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27579 Bug ID: 27579 Summary: Add field for creator to Manage staged MARC records Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org When viewing the list of .mrc files in Manage staged MARC records it would be helpful to be able to see which logged in user created/imported the batch of records. It would enable staff to contact the person in case there are questions about the content or status of the file. It seems like this could be similar to the 'Author' field that displays for saved reports which shows the name of the Koha user and their patron record number. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 27434] New: Task Scheduler should use classes as job types
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '26

18 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27434 Bug ID: 27434 Summary: Task Scheduler should use classes as job types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Task Scheduler Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Rather than maintaining a list of types and going through each case we should use the class as the job type so we can call it directly -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 23919] New: Make ISSN searchable with and without hyphen
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23919 Bug ID: 23919 Summary: Make ISSN searchable with and without hyphen 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For the ISBN we have the option to activate search with and without hyphens - but this doesn't work for ISSN. We shoudl make it work there as well. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56