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

[Bug 25334] New: Add generic 'phone' message transport type
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25334 Bug ID: 25334 Summary: Add generic 'phone' message transport type 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org As bug 25333 changed the 'phone' transport type to 'talkingtech', we can now re-add 'phone' as a transport type again, and allow it to behave and support the same notices as the email transport type. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 21591] New: Data inconsistencies - Item types and biblio level
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21591 Bug ID: 21591 Summary: Data inconsistencies - Item types and biblio level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz bug 21150 added a script to check for missing item level itemtypes - it doesn't like when both the item and the record are missing itemtype -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 22328] New: Inconsistent behavior throughout acquisitions for determining whether or not an item as been received
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '20

20 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22328 Bug ID: 22328 Summary: Inconsistent behavior throughout acquisitions for determining whether or not an item as been received Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- When an aqorders line has quantityreceived>0 but datereceived is NULL, fund totals shows inconsistently across acquisitions. To test: - create an order with quantityreceived=1 and datereceived NULL (this may need to be done from the command line) - find the relevant fund in the All Available Funds table at acqui-home.pl, note that the order is reflected in the Spent total - Click through to spent.pl for the relevant fund, note that the order is not reflected here - Click through to ordered.pl for the relevant fund, note that the order is not reflected here either I'll acknowledge that it shouldn't really be possible for an item to have a quantityreceived without a datereceived -- I haven't yet figured out how the library I found this on did it -- but the inconsistent logic is an issue nonetheless. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24012] New: Display 'Locked' budget in red
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '20

19 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24012 Bug ID: 24012 Summary: Display 'Locked' budget in red Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I find it illogical that the 'Locked' in locked budget is displayed in green. Shouldn't it be displayed in red? To reproduce: 1- Go to Administration 2- Click on Budgets 3- Add a new budget and check the 'Lock budget' box 4- Click on the 'Inactive budgets' tab 5- Note that 'Locked' is displayed in green -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 24306] New: Add debug option to koha-indexer
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '20

19 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24306 Bug ID: 24306 Summary: Add debug option to koha-indexer 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Would be nice to be able to raise logging level and see errors from the indexer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 21066] New: Use opac_news.timestamp as a real timestamp or add opac_news.updated_on ?
by bugzilla-daemon＠bugs.koha-community.org 19 Nov '20

19 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21066 Bug ID: 21066 Summary: Use opac_news.timestamp as a real timestamp or add opac_news.updated_on ? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org I would propose to use the opac_news.timestamp field readonly and fill/update it automatically via SQL. Or do we still need the original publish date and add a modified/updated_on timestamp? What do you think? -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 25167] New: Fix to a fix wrong inventory results
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25167 Bug ID: 25167 Summary: Fix to a fix wrong inventory results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hi, Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12913 solves the case when notforloan filter is not used, but it breaks the case when a filter is used. Regards Didier -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 23432] New: Stock rotation: cancelled transfer result in stockrotation failures
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23432 Bug ID: 23432 Summary: Stock rotation: cancelled transfer result in stockrotation failures Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: bugzilla(a)koha-us.org, gmcharlt(a)gmail.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org Depends on: 22566, 22569 Blocks: 23092 If one cancels a transfer that has been initiated via StockRotation, then the next call to the stockrotation cronjob will fail due to a 'die' line when said transfer can no longer be found. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22566 [Bug 22566] Stock rotation cronjob reporting has issues https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22569 [Bug 22569] Stock rotation: need transfer reports https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23092 [Bug 23092] Transfers should record 'requested' as well as 'sent' and 'arrived' dates. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 23828] New: Elasticsearch - ES - Authority record results not ordered correctly
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23828 Bug ID: 23828 Summary: Elasticsearch - ES - Authority record results not ordered correctly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com For example: Catholic Church Addresses, essays, lectures Catholic Church El Salvador Addresses, essays, lectures . . . Catholic Church. The 'El Salvador' displays first, but is sorted as coming after Address... Catcholic hcurch with an ending period comes after Catholic Church with subfields We should ideally generate the sort fields in the same order that fields are listed in the record - that seems to be how the display of results is formed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 23118] New: Move PayPal logic to plugin
by bugzilla-daemon＠bugs.koha-community.org 17 Nov '20

17 Nov '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23118 Bug ID: 23118 Summary: Move PayPal logic to plugin Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Move PayPal to a plugin, to unify treatment of payment methods. This bug should simply remove PayPal logic from intranet and opac and place it as a plugin, with necesary configurations. It will be downloadable from https://gitlab.com/thekesolutions/plugins/koha-plugin-paypal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18