Required surveys force responses even when responses exist

Bug #793585 reported by Bill Erickson
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Medium
Unassigned

Bug Description

Evergreen 2.0.

In the patron registration interface, if a survey is marked as 'required', it is not possible to save a user until a response to the server has been entered. That's fine, however, previous responses to surveys do not show up in the registration interface, which creates a scenario where staff are forced to re-enter responses every time they edit a given user (which creates multiple responses in the database).

Presumably, previous responses are not shown because a user can in theory have multiple responses to a survey.

We either need to fill in the value of (say) the last response to each survey or simply treat the survey as not required if any responses exist.

Changed in evergreen:
status: New → Confirmed
tags: added: 2.0 patron registration staffclient survey
Revision history for this message
Mike Rylander (mrylander) wrote :

The existing behavior is the originally intended behavior, so perhaps a new flag on surveys to make them continually required vs only required once would be better than changing the behavior outright.

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Setting to incomplete until someone confirms Mike's suggestion.

tags: removed: 2.0
Changed in evergreen:
status: Confirmed → Incomplete
Revision history for this message
Erica Rohlfs (erohlfs) wrote :

Good Afternoon!

Mike has a wonderful suggestion.

Bill raises the concerns addressed in this topic for Evergreen version 2.0.

Now in version 2.5.0, a required survey still causes confusion.

As Bill mentions, a required survey must be answered each and every time a staff member edits the patron account (within the Edit tab of the patron’s account). This requirement in and of itself is not necessarily the source of confusion. Staff members do not always know why the patron information will not save.

Attached is a screen image of trying to save the patron’s information when a required survey has not been answered.

As you can see, there is not any discernable indication as to why the information won’t save.
(Please Note: The patron in the image is fictional)

Changed in evergreen:
status: Incomplete → Confirmed
tags: added: surveys
removed: survey
tags: added: webstaffclient
removed: registration staffclient
tags: added: usability
Changed in evergreen:
importance: Undecided → Medium
tags: removed: webstaffclient
Gina Monti (gmonti90)
tags: added: angularjs
Revision history for this message
Terran McCanna (tmccanna) wrote :

Currently testing in the 3.8 release candidate with the AngularJS patron form and the Angular surveys interface, and it looks like the opposite behavior is occurring now - even when a survey is marked as required, it's not requiring an answer to save the patron account.

Revision history for this message
Andrea Neiman (aneiman) wrote (last edit ):

Confirming what Terran notes in comment #4 in master as of 3/17/22 - marking this bug won't fix and opening a new one.

Changed in evergreen:
status: Confirmed → Invalid
status: Invalid → Won't Fix
Revision history for this message
Andrea Neiman (aneiman) wrote :
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.