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

[Bug 38299] New: Errors with updates caught in C4::Installer should be colored/highlighted
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38299 Bug ID: 38299 Summary: Errors with updates caught in C4::Installer should be colored/highlighted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com We introduced color into our db update output, but we never implemented it in the upstream code that catches database level failures. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 37880] New: Unwanted form submission on RenewAll button
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37880 Bug ID: 37880 Summary: Unwanted form submission on RenewAll button Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38702] New: Random number entered into 952$e when receiving
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38702 Bug ID: 38702 Summary: Random number entered into 952$e when receiving Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To Replicate 1. Check the Default framework and ensure the 952$e is available. 2. Set up the vendor and basket. Have items created when ordered 3. Create a basket and add some orders. 4. Close the basket. 5. Check the item record that was generated for the orders. Notice the 952$e is blank. 6. Receive the orders. 7. Now look at the items again and see a random number has been entered into the 952$e. A number should not be added to the 952$e.Tested with MarcItemFieldsToOrder configured and also blank and the number appears regardless. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 38700] New: Add items table field to record transfer status
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38700 Bug ID: 38700 Summary: Add items table field to record transfer status Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Checking whether or not an item is currently in-transit using SQL is more complicated than one would like. We know an item is currently in-transit if there is a line in branchtransfers with that itemnumber, with a date sent, and without either a date cancelled or a date received. I suggest we add a field to items that would work like items.onloan does for issues. We name the field items.intransit and when the transfer is sent we put something in the field (either the transfer ID or the branch to which the item is headed) and when the transfer is either completed or cancelled we null items.intransit. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #22 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Using cn_sort is the standard way of doing this, I don't believe there is a better way than using the sorting form of the callnumber. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38332] New: Add more info about the checkout to SCO module
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38332 Bug ID: 38332 Summary: Add more info about the checkout to SCO module Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the selfcheck module if you check out, renew, or check in an item you see this: Item checked out ([% barcode | html %]) Item renewed ([% barcode | html %]) Item checked in ([% barcode | html %]) It would be nice if we could include a bit more info here, particularity title. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38716] New: Add table configuration to Hold A Specific Item table in staff interface
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38716 Bug ID: 38716 Summary: Add table configuration to Hold A Specific Item table in staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The table showing items available for an item-specific hold in the intratnet (requestspecific on request.pl) has a hardcoded set of item fields visible. It would be helpful to add column configuration here so a library can hide those columns. We could then add more columns as optional. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #21 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #20) > Sorry, I am not sure I get your point. :( > > For me this patch for sorting and the generation of cn_sort are separate. > > cn_sort is generated whenever an item is edited/changed, or the touch script > is run, depending on the classification source. Of course there can be bugs > in this area too. > > For sorting we use cn_sort already in other places like inventory or the > callnumber value builder and the field should be used every where we sort on > callnumbers. > > For me the goal of this patch is to use the cn_sort data. So I'd probably > look at the itmecallnumber, cn_sort and sort by cn_sort with SQL and compare > that to what I see in item search. I would think that the goal of this report is getting the sort correct. How we do that, is another thing. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 16 Dec '24

16 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #20 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Sorry, I am not sure I get your point. :( For me this patch for sorting and the generation of cn_sort are separate. cn_sort is generated whenever an item is edited/changed, or the touch script is run, depending on the classification source. Of course there can be bugs in this area too. For sorting we use cn_sort already in other places like inventory or the callnumber value builder and the field should be used every where we sort on callnumbers. For me the goal of this patch is to use the cn_sort data. So I'd probably look at the itmecallnumber, cn_sort and sort by cn_sort with SQL and compare that to what I see in item search. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14907] Item search: Call Numbers in Item search results are ordered alphabetically
by bugzilla-daemon＠bugs.koha-community.org 15 Dec '24

15 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14907 --- Comment #19 from Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Katrin Fischer from comment #18) > (In reply to Marcel de Rooy from comment #17) > > (In reply to Katrin Fischer from comment #16) > > > But isn't this more a question of how the cn_sort is generated instead of > > > making sure it's using cn_sort for sorting? > > > > These are tightly coupled of course. > > Coupled yes, but this bug doesn't deal with the generation. This bug deals about sorting? So we should use cn_sort and make sure that cn_sort is filled correctly. -- You are receiving this mail because: You are watching all bug changes.

1 0