Issue Details (XML | Word | Printable)

Key: CSRVY-4
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Frank Stiller
Reporter: hajo van Ravenswaay
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Confluence Survey Plugin

Skip option/subquestions

Created: 03/Jun/08 04:01 AM   Updated: 06/Jun/08 05:47 AM
Component/s: survey-macro
Affects Version/s: 1.1.6
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Confluence

Labels:


 Description  « Hide
In a survey one might like to ask for more detail if a respondent answers possitive/negative on a question, while an opposite answer might imply a number of questions are not relevant anymore. Therefore it is necessary to set up an option to ask additional questions if an particular answer is given.

For this I see two scenario's;
1. Skip option; if a respondent answers X (instead of Y) on a question, a number of additional questions is skipped.
2. Sub questions; a main question is created, only if a respondent answers a specific answer additional subquestions will be asked.

For example;
Do you like alcoholic beverages?
=> If answered yes; ask subquestions. E.g. what alcoholic beverages? Beer, Bacardi, mix, cocktail, etc.
=> If answered no; go to next question.



 All   Comments   Work Log   Change History   FishEye   Crucible   Builds      Sort Order: Ascending order - Click to sort in descending order
Frank Stiller added a comment - 03/Jun/08 04:20 AM
with the current architecture it would only be possible by a survey-parameter. You cant say that on a vote-line really clever.

I am thinking on a change in architecture, like:

{survey}
{vote}{survey}

but that would lead to a need of a upgrade class, like the dynamictasklist-macro. Quite complicated to change by the way.

Would that be ok to "just have" the Survey-Parameter?


hajo van Ravenswaay added a comment - 06/Jun/08 04:47 AM
Frank, I miss what you mean by a Survey-Parameter. Could you calrify this? Thnx

Frank Stiller added a comment - 06/Jun/08 05:15 AM
A survey is a set of vote macros.

But the survey macro is limited in its architecture, as it just parse the lines in the macro body. With a modular Macro-Architecture like mentioned here you could say on every survey-item {vote:id=1|QType=YesNo|SkipOnOption=2} that would be more straightforward (where the second option, here no would skip the next Question/s).

But with the current state something like {survey:SkipOption=3|SkipNext=2} would be possible. So every Question with the 3rd Option voted will skip the next 2 Questions for the survey-attendee.


hajo van Ravenswaay added a comment - 06/Jun/08 05:47 AM
OK, I get it. This way the {survey} macro could be just great, because it offers more flexibility in the questions which can invoke a skip option. Hower, the survey macro does not allow custome answers, whereas the vote macro does.