https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190

Michaela Sieber <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Patch doesn't apply         |Failed QA

--- Comment #270 from Michaela Sieber <[email protected]> ---
Today testing results:

1.) Still problems with permissions: 
  - permission error 403 with restricted user 

192.168.56.1 - - [11/Feb/2026:16:29:39 +0000] "GET
/api/v1/app.pl/api/v1/patron_categories?_per_page=-1 HTTP/1.1" 403 -
"http://192.168.56.101:8081/cgi-bin/koha/admin/circulation_triggers";   
192.168.56.1 - - [11/Feb/2026:16:29:40 +0000] "GET
/api/v1/app.pl/api/v1/circulation_rules/config HTTP/1.1" 403 -
"http://192.168.56.101:8081/cgi-bin/koha/admin/circulation_triggers";  


 To reproduce : Edit an existing borrower (e.g. Casey King) and give
Permissions for staff, reports and manage_circ_rules and
edit_notice_status_triggers

Login with this user. Verify that you see Circulation Triggers under
Administration. Click on Link "Circulation Triggers" , then you see the error
above for two seconds before you are redirected to Koha start page.

Question : is the permission edit_notice_status_triggers still relevant? It is
still under Tools and not under  "Manage Koha system settings (Administration
panel) (parameters)"


2.) default x-Button in transport types (Modal edit trigger) 
 - for users it seems that only one transport type is possible

To reproduce : Edit a trigger and go to the section "Edit notice for trigger x"
select a letter, this adds a new line for transport types with the mentioned
default x-Button that prevents to add more than one transport type (e.g.
Print+email)

3.) Transport type should be required field if letter exists
It makes no sense to have a notice without a definition how the notice is sent.
The transport type should therefor be a required field


@ChloƩ : I've sent you Screenshots in Mattermost


4.) Migration scenario 

We found some odd behavior but need more time to document the scenario.

TBC

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to