Extra Step needed to remove email notification option using the Edit Notification Settings

Bug #1897798 reported by Dale Rigney
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Tested in Evergreen 3.3. and Evergreen 3.4:

If a hold has the e-mail notification option checked and staff try to remove the notification option in the Web Client they have to use and extra step that is not needed when removing the phone or SSM options. When in the holds screen of a patron here are the steps that is needed to remove the email option:

1) Right click on the hold.
2) Select "Edit Notification Settings".
3) In the pop up window click on the box to the left of "Send Emails".
4) A box will pop up on the right of the "Send Emails", click on that box to enable a check in the box.
5) Click on the right box again to remove the check mark.
6) Click on the submit button.

To remove the phone notification option you just have to click on the box to the left of the phone number, then click on the submit button. You do not need to enter something in the phone number box to the right of the option for the process to work. removing the SSM notification option is the same as the phone notification option. The email notification option is the only option where you have to toggle the box on the right on and then off again before hitting the submit button for the process to work.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
tags: added: holds usability
Revision history for this message
Terran McCanna (tmccanna) wrote :

The overall usability of that popup could be improved, as it doesn't reflect the current state of whatever hold(s) is being edited. See also: https://bugs.launchpad.net/evergreen/+bug/1908618

Dan Briem (dbriem)
tags: added: circ-holds
removed: holds
Gina Monti (gmonti90)
tags: added: tt2
Revision history for this message
Lindsay Stratton (lstratton) wrote :

Confirm this is still the situation in 3.6.

Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Confirmed this is still an issue in 3.8

Revision history for this message
Shannon Dineen (sdineen) wrote :

Confirmed this is still an issue in 3.9. on our production servers, and in 3.9.1 on test servers.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.