View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
07453 | Feature requests | Conditions | public | 2010-11-17 19:35 | 2021-11-15 08:56 |
Reporter | lwc | Assigned To | galads | ||
Priority | normal | Severity | feature | ||
Status | closed | Resolution | fixed | ||
Summary | 07453: Surveyors should approve their answers | ||||
Description | It's frustrating for everyone involved when surveyors detect wrong answers in their post-submit "print answers" link, only to realize by then it's too late. Such a feature would create more reliable and more user friendly surveys. See more details in http://www.limesurvey.org/support/forums/20/52495 | ||||
Additional Information | A possible solution: Force surveyors to approve their answers Of course, make it an on/off option so each admin could decide whethere to force it or not. | ||||
Tags | No tags attached. | ||||
Bug heat | 6 | ||||
Story point estimate | |||||
Users affected % | |||||
I dont like the idea because many surveys relie on the fact, that the participant does not have the abbility to oversee all of his answers! An on/off option would be possible, but overall it isnt worth it. You should add a "Dont care" button to ideas, but solutions! |
|
Alternative solution: INSERTQUESTION Replacement Field Code A quick button to spit out all of them would be pretty great too. |
|
I think this is a basic need as any survey that lets you print your answers lets you see all of them after submission, so why not let you see them before submission to make sure they are right without having to scroll through many pages. I have a 10+ page survey I'm setting up now and this is a requirement so I will have to manually copy and paste questions and use INSERTANS to show answers on a boilerplate question which is not very efficient and is prone to error. As such, I have added a simpler solution that would let you create a page like this but at the very least reuse question text. |
|
Dear lwc , Thank you for suggesting a feature. However, we will not be picking this up because the use case is too specific or the use case might not fit to the latest versions of LimeSurvey. Other reasons why the feature is dropped could also be, it has been implemented already. Please check on the latest versions and if the issue still exists, feel free to re-open the report. kind regards, |
|