Bug 15982

Summary: Serials numbering patterns can be deleted without warning
Product: Koha Reporter: Owen Leonard <oleonard>
Component: SerialsAssignee: Owen Leonard <oleonard>
Status: CLOSED FIXED QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: brendan, colin.campbell, f.demians, julian.maurice, testopia
Version: Main   
Hardware: All   
OS: All   
URL: /cgi-bin/koha/serials/subscription-numberpatterns.pl
Change sponsored?: --- Patch complexity: Small patch
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Bug 15982 - Serials numbering patterns can be deleted without warning
Bug 15982 - Serials numbering patterns can be deleted without warning
Bug 15982 - Serials numbering patterns can be deleted without warning

Description Owen Leonard 2016-03-04 17:00:45 UTC
When the user tries to delete a serials numbering pattern there should be a JavaScript alert asking for confirmation.
Comment 1 Owen Leonard 2016-03-04 17:09:34 UTC Comment hidden (obsolete)
Comment 2 Nicole C. Engard 2016-03-08 20:37:34 UTC Comment hidden (obsolete)
Comment 3 Jonathan Druart 2016-03-09 11:05:54 UTC
Created attachment 48843 [details] [review]
Bug 15982 - Serials numbering patterns can be deleted without warning

A JavaScript alert should ask the user to confirm deletion of a serial
numbering pattern. This patch adds this to the template.

To test, apply the patch and go to Serials -> Manage numbering patterns.

- In the list of patterns, click any "Delete" link.
- Verify that a JavaScript alert is triggered.
- Test that cancelling the alert cancels the deletion operation.
- Test that confirming the alert allows the deletion to complete.

Signed-off-by: Nicole C Engard <nengard@bywatersolutions.com>

Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Comment 4 Brendan Gallagher 2016-03-09 16:27:08 UTC
Pushed to Master - Should be in the May 2016 release.  Thanks!
Comment 5 Julian Maurice 2016-03-14 09:27:27 UTC
Patch pushed to 3.22.x, will be in 3.22.5
Comment 6 Frédéric Demians 2016-03-15 09:04:42 UTC
This patch has been pushed to 3.20.x, will be in 3.20.10.