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

[Bug 35049] New: Add ability to choose which status is included in MaxOpenSuggestions
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35049 Bug ID: 35049 Summary: Add ability to choose which status is included in MaxOpenSuggestions 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org This is following a discussion between me and Aude on https://gitlab.com/koha-community/koha-manual/-/merge_requests/739 A client asked me if their custom status was included in the count for MaxOpenSuggestions. After testing, I found that only "Pending" suggestions were counted. This was fine with my client as it is what they wanted. But Aude raised the question that maybe some libraries might want their custom statuses to be included in the count. My client did ask me in the inital request that if the suggestions with custom statuses were included in MaxOpenSuggestions, if it was possible to "add an exception" to make it not count... I think it depends on the workflow of the library. If the status is s step after the suggestion has been analysed and decided upon, it probably should not count in MaxOpenSuggestions. But if it's a status for open suggestions waiting for analysis by another staff member (for example), it probably should count. I was thinking a system preference might be added, similar to the ILLHiddenRequestStatuses syspref, to let the library choose which statuses count in MaxOpenSuggestions. By default, only 'Pending' counts. To test: 1. Change MaxOpenSuggestions to 2 2. Go to Adminsitration > Authorized values > SUGGEST_STATUS and add a custom status 3. Log in to the OPAC as a patron 4. Make 2 suggestions --> A message should indicate that you cannot make any more suggestions as you have reached the maximum permitted 5. In the staff interface, go to Acquisitions > Suggestions 6. Change the status of one of the suggestions to the custom status 7. Go back to the OPAC --> You should now be able to make a suggestion -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18298] New: Enforce password complexity
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18298 Bug ID: 18298 Summary: Enforce password complexity Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries would want to add the option to Koha to enforce a strong password policy. That policy would mean that passwords should include both upper and lower case characters one or more numbers. -- You are receiving this mail because: You are watching all bug changes.

1 91

[Bug 33985] New: Add the ability to integrate electronic signatures
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33985 Bug ID: 33985 Summary: Add the ability to integrate electronic signatures 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A library would like to be able to integrate electronic signatures into Koha. This could be a way that the patron could sign digitally and this signature would be captured in Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 35832] New: Add option to include an email signature on all notices
by bugzilla-daemon＠bugs.koha-community.org 04 May '25

04 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35832 Bug ID: 35832 Summary: Add option to include an email signature on all notices 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to have the option to always include a particular signature on all notices from the system. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 38090] New: The UX for customer notice styling per notice template is confusing
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38090 Bug ID: 38090 Summary: The UX for customer notice styling per notice template is confusing Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A couple of people have highlighted now that the adding of a 'Format' section amongst the message transport types in the notice template editor is confusing. The feature itself is also a little misleading as people presumed from the title that it affected print-type notices only, when in fact it affects all notice types when printed. The distinction is subtle, but makes a large difference in expectations. I'm not sure how to proceed here, but I want it recorded as a bug to see if anyone can come up with a cleaner approach for end users. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 17406] New: Simplify pay.pl interface - pt.1
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17406 Bug ID: 17406 Summary: Simplify pay.pl interface - pt.1 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I think we can simplify the payment screen. 1) Remove the Pay Amount button. By default, all items are selected, so the Pay selected will do the job. 2) Remove the cancel link. A) It's a link, not a button. B) All it does is change tabs. There isn't anything to really cancel. Changing tabs or navigating elsewhere does the same thing. 3) Remove Write off all button and replace with Write off selected button. 4) Remove the individual Pay and Write off buttons. They are redundant. #4 is my opinion, but they really convolute the flow. The checkboxes and two buttons are sufficient and straight forward. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 35597] New: Purchase Suggestion changes aren't logged
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35597 Bug ID: 35597 Summary: Purchase Suggestion changes aren't logged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org IT would be helpful if changes to purchase suggestions were logged. Sometimes troubleshooting the cycle of a suggestion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 36253] New: Port default acquisition notices to Template Toolkit syntax
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36253 Bug ID: 36253 Summary: Port default acquisition notices to Template Toolkit syntax Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: roadmap_24_05 Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 There are 3 acquisitions notices that still use "hungry alligator" syntax: ACQ_NOTIF_ON_RECEIV ACQCLAIM ACQORDER ACQCLAIM and ACQORDER are very similar, and it would make sense to do them together. ACQ_NOTIF_ON_RECEIV is pretty brief and simple, so we might as well bundle it in too. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36417] New: Add TT notices to acquisition claim notices
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36417 Bug ID: 36417 Summary: Add TT notices to acquisition claim notices 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 31858 It would be great if we could make TT usable in the Acq claim notices the same way we did for ACQORDER in bug 31858. The notices are usually very similar and require the same access to data. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31858 [Bug 31858] TT syntax for ACQORDER notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 31988] New: manager.pl is only user for "Catalog by item type" report
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31988 Bug ID: 31988 Summary: manager.pl is only user for "Catalog by item type" report Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is an odd script - it looks like the intent was to have one script that could call various reports. We have a single "plugin" for the reports - itemtypes.plugin We should convert this to a regular report script -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23