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

[Bug 28787] New: Send a notice with the TOTP token
by bugzilla-daemon＠bugs.koha-community.org 02 Mar '23

02 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28787 Bug ID: 28787 Summary: Send a notice with the TOTP token 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 28786 Bug 28786 will let librarians enable a Two-factor authentication but will force them to use an application to generate the TOTP token. It would be nice to have the ability to send a notice with the code, via email or SMS. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28786 [Bug 28786] Two-factor authentication for staff client - TOTP -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 107

[Bug 31890] New: PrefillGuaranteeField should include option to prefill surname
by bugzilla-daemon＠bugs.koha-community.org 02 Mar '23

02 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31890 Bug ID: 31890 Summary: PrefillGuaranteeField should include option to prefill surname Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The PrefillGuaranteeField system preference does not allow for the copying of the surname field, I think it should. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 31537] New: Elasticsearch - index mapping for 003 control-number-identifier is twice in mappings.yaml
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31537 Bug ID: 31537 Summary: Elasticsearch - index mapping for 003 control-number-identifier is twice in mappings.yaml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com Hi all! I'm not sure if it's for a specific purpose, but the index mapping for 003 control-number-identifier was added twice in the mappings.yaml file. In Bug 28830 and Bug 11175. If it's not necessary that it be there twice, I propose we remove it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 28830] New: Add CNI (Control Number Identifier) search index
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28830 Bug ID: 28830 Summary: Add CNI (Control Number Identifier) search index Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We ought to have a cni index to allow searching on the content of the 003 marc field for accurate linking using UseControlNumber type searches. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 28535] New: Show item type for checkouts in OPAC
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28535 Bug ID: 28535 Summary: Show item type for checkouts in OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: rickard.lindfors(a)sh.se QA Contact: testopia(a)bugs.koha-community.org In the OPAC, when the user is logged in, checkouts are being showned. We would like to also show the item type on each checked-out item. It seems to possible to do this with the system preference "item-level_itypes", but unfortunately, that seems to affect a lot of other things. It would be to a have a system preference like "ShowItemTypeInOPAC" that only affects just that. (Also, I might miss something, and there might be some other alternatives, of course). -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 17699] New: DateTime durations are not correctly subtracted
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '23

01 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17699 Bug ID: 17699 Summary: DateTime durations are not correctly subtracted Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16911 >From DateTime::Duration pod: """ For positive durations, the "end_of_month" parameter defaults to wrap. For negative durations, the default is "limit". This should match how most people "intuitively" expect datetime math to work. """ Today we are Nov 30, that means $today->subtract( months => 1 ) will return Oct 31, when we usually expect Oct 30 in tests Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16911 [Bug 16911] Koha::Patrons - Move ExtendMemberSubscriptionTo to ->renew_account -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 22417] New: Delegate background jobs execution
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 Bug ID: 22417 Summary: Delegate background jobs execution Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This is related to: Bug 15032 - [Plack] Scripts that fork (like stage-marc-import.pl) don't work as expected Bug 1993 - Task Scheduler Needs Re-write And many others. The goal here would be to remove the background execution in real time we are doing right now and delegate the jobs to an external service (handling several workers, load balancing, etc.) -- You are receiving this mail because: You are watching all bug changes.

1 422

[Bug 29165] New: Allow patron modification request notifications to be branch specific
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '23

28 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29165 Bug ID: 29165 Summary: Allow patron modification request notifications to be branch specific Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a patron makes request via the OPAC to change some of their patron details librarians get a notification on the staff main page about the request. Some multi-branch systems find this confusing because they see all the requests across all the branches. It would be nice if this were filtered to only the current logged in branch. But maybe some libraries like the current behavior, so maybe this could be a system pref? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26923] New: Batch modification for Reports
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26923 Bug ID: 26923 Summary: Batch modification for Reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org It would be useful to update some datas for several reports at a time when selecting them. For more security, only the following fields could be updatde : - group - sub-group - public - Cache expiry -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 21263] New: Pickup library not set correctly when using Default holds policy by item type
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '23

27 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21263 Bug ID: 21263 Summary: Pickup library not set correctly when using Default holds policy by item type Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Not sure if this is a bug or just me misunderstanding the options - Make sure OPACAllowUserToChooseBranch is set to don't allow - Make sure you have two branches A and B - Have one item whose homebranch is B - Have one user whose homebranch is A - Make sure the circulation rules allow the user to reserve the item's item type 1. Go to Administration > Circulation and fines rules 2. Create a Default holds policy by item type for that item type - Item type = item's item type - Hold policy = From any library - Hold pickup library branch = item's home library - Return policy = item returns home 3. Go to the OPAC and log in with the user's credentials 4. Search for the item 5. Click on "Place hold" 6. Confirm hold 7. In the user's file on the OPAC and check the reservation's pickup library What I understand : - Hold policy = From any library: Users from any library can reserve this item type - Hold pickup library branch = item's home library: the pickup library must be the item's homebranch (in this case, B) - Return policy = item returns home: upon return, the items is transferred to its homebranch Therefore, the pickup library in the case above should be B, but it is automatically set to A. P.S. note that I have item-level_itypes set to specific item, and Item level holds set to don't allow. I feel like in this case it should maybe fall back to the record-level item type? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13