I have a preview for a single question which is really helpful.

I would like to have as well a preview of a Question Group. This would help me to get an idea about the order and being lost in details. Would help especially for those questions at the end of a survey.

Make the infos like browser agent, javascriptversion, OS and additonal infos available in the results.

Some workarounds are not working with different browsers. E.g. you wonder why a hidden question was filled out with a invalid value (solution, very old browser wasn't hiding the question). If you have the additional infos at hand you can quickly pinpoint what might be the cause of that answer pattern.

The variables could also be made accessible for conditions.
But to save them into the results would be already a big help to give feedback about problems and weighting them in terms of how often they would occur in the field.

I use the same survey, except for a few small changes, with different groups of people. I'd like the ability to just click a button and copy a survey, including questions, layout, etc., without needing to use the import/export feature.

Survey settings is composed of 2 pages:
1 Survey configs, with tuples (name-value) .e.g. Allow Saves Y/N
2 Survey textes, with survey title, welcome, endmsg.

The first part of settings are set at start of your work with a survey, and rarely fixed later.
The behaviour of a survey is technical choice, with a tendency of no change over time.

The second part is very frequently used, I believe it stays at the same level of questions and aswer, often modified for the same aesthetic or pratic reasons.

All possible transitions (of pages, of state) a survey can undergo by user interaction are:
- start
- resume a survey
- save the survey
- cancel and exit
- go prev
- go next
- end

The state of the art is a non-homogeneous implementation:
- Exit and clear = < a> tag with a fixed url carrying a crucial get parameter
- Load unfinished = < input> tag with type="submit" and crucial value "Load unfinished survey"
- Save = < input> tag with type="submit" and crucial value "saveall"
- < < prev = < input> tag with type="Submit" and crucial value "< < Prev"
- next>> = < input> tag with type="Submit" and crucial value "Next>>"
- start = < input> tag with type "Submit" and crucial value "movenext"
- end = < input> tag with type "submit". Value unknown at the time of writing this.

These should be harmonized: use the same tag and discriminate over one (single) parameter.

When you want to style question for an individual survey you have to manually include a css file or edit the overall template. It would be nice to have additional, surveyspecific CSS in a separate CSS file that can be edited from the survey screen instead of from the template editor.