Required surveys force responses even when responses exist
Bug #793585 reported by
Bill Erickson
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 |
tags: |
added: surveys removed: survey |
tags: |
added: webstaffclient removed: registration staffclient |
tags: | added: usability |
Changed in evergreen: | |
importance: | Undecided → Medium |
tags: | removed: webstaffclient |
tags: | added: angularjs |
To post a comment you must log in.
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.