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

[Bug 16117] New: Feature request: Log borrower cardnumbers and item barcodes which are not valid
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16117 Bug ID: 16117 Summary: Feature request: Log borrower cardnumbers and item barcodes which are not valid Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On any circ screen where a barcode could be scanned (circ.pl, checkin.pl, checkout and return boxes), we should have the option of logging failed barcode scans, for the purpose of trouble-shooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 17337] New: waitingreserves.pl should trigger transfers as well as holds
by bugzilla-daemon＠bugs.koha-community.org 10 Feb '24

10 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17337 Bug ID: 17337 Summary: waitingreserves.pl should trigger transfers as well as holds Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Bug 17010 addresses triggering the next hold when a hold is cancelled, but transfers should also be triggered. Currently in 3.22.8 nothing happens. It is unclear if 17010 addresses transfers as well. Also, in 3.18 local holds were spotty when holds were triggered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 17755] New: Move C4::Members::AttributeTypes to Koha::* namespace
by bugzilla-daemon＠bugs.koha-community.org 31 Jan '24

31 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17755 Bug ID: 17755 Summary: Move C4::Members::AttributeTypes to Koha::* namespace Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 16440] New: Update report parameters
by bugzilla-daemon＠bugs.koha-community.org 10 Jan '24

10 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16440 Bug ID: 16440 Summary: Update report parameters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 51217 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=51217&action=ed… Placement of report parameters on report results. Let's say you have a report that asks you for parameters. You run the report, get the results, and then you want to run the report again with different parameters. Or maybe you made a mistake and need to change it. Yes, you could back up and change things and run it again. But what if the parameters were showing over on the left of the report under the "Useful resources" section? You could see what you set, and change whatever you needed and then click update. Perhaps the row setting and update button could also be on the left of the report. Just a thought. I was able to change a parameter up in the URL, and hit update, and it worked. It was nice because I set the report to show more than 20 records, and I didn't have to repeat that step after updating. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 17735] New: Merge boraccount and pay pages into one
by bugzilla-daemon＠bugs.koha-community.org 10 Dec '23

10 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17735 Bug ID: 17735 Summary: Merge boraccount and pay pages into one Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We don't really need to have this agenda on two pages - using the one pages would be simpler and makes the workflow more straightforward -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 16959] New: E-mail alerts for saved searches
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16959 Bug ID: 16959 Summary: E-mail alerts for saved searches 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha allowed to send e-mails to patrons when a new record is created for a saved search. Examples: - New records are added within a specific call number range - New records where the title contains certain words It should be possible to set this up individually per patron. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17499] New: Koha objects for messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17499 Bug ID: 17499 Summary: Koha objects for messaging preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Create Koha objects for messaging preferences. We need to create REST API endpoint for managing patron messaging preferences and this is the first step. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 241

[Bug 15977] New: Optional double screen message in Patron Info/Status
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15977 Bug ID: 15977 Summary: Optional double screen message in Patron Info/Status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This code in MsgType.pm: $resp .= maybe_add( FID_SCREEN_MSG, $patron->{branchcode}, $server ) if ( $server->{account}->{send_patron_home_library_in_af} ); produces two AFs if you enable that attribute in your config. Not sure if that should be the case and is conform protocol. Also: are we solving a problem here in the wrong place? It looks kind of inappropriate use.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 17228] New: Make two versions of SIPconfig.xml identical
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '23

23 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17228 Bug ID: 17228 Summary: Make two versions of SIPconfig.xml identical Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Packaging Assignee: magnus(a)libriotech.no Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net We have two versions of SIPconfig.xml: etc/SIPconfig.xml debian/templates/SIPconfig.xml The former has been updated with some changes to the possible configuration of SIP2 servers, e.g. by bug 15006. The latter has not been updated with the same information. Since debian/templates/SIPconfig.xml contains no special placeholders or variables, this bug proposes to simply copy etc/SIPconfig.xml to debian/templates/SIPconfig.xml, so that admins using the packages will see an up-to-date SIP2 config example when they have enabled SIP2 for a site. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 17047] New: Mana webservice : share and use common information between Kohas
by bugzilla-daemon＠bugs.koha-community.org 04 Oct '23

04 Oct '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17047 Bug ID: 17047 Summary: Mana webservice : share and use common information between Kohas Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: morgane.alonso(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org RFC : https://wiki.koha-community.org/wiki/SharingDatasBetweenKohas_rfc Progress of the Mana features : https://wiki.koha-community.org/wiki/Mana_central_database -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 536