Question type similar to a DualScale question type.

Difference is that you that you are not allowed to choose the same item on both scales.

Simple example would be : First scale "most important", second scale "least important". Now you show different items to choose from. With a dual scale question type it would be possible to choose the same item as "most important" AND "least important" which wouldn't allow to apply the MaxDiff method.

http://www.limesurvey.org/en/support/forums/5-can-i-do-this-with-limesurvey/259 71-maxdiff-question-style-available-or-workaround

Allow hiding Welcomepage (when you are linking different surveys together) or different Endpages (e.g. respondents get suitable redirection).

During the development of the survey and in the pretest phase you often need to test certain parts and need to get feedback from certain stakeholders of a survey.

To get to certain parts of the survey it would be good to be able to skip conditions and validation rules and skip back and forth through the survey.

It would be nice if comments could be placed on the questionspage instead of collecting them via phonecalls and emails.

The setting of $rooturl = "http://$_SERVER['HTTP_HOST'] only allows you to set https or http . No casewise SSLencryption.

Often installations are using selfsigned certs which will produce cryptic messages beside adding load when just delivering surveys to respondents.

A workaround is leaving the $rooturl empty. But that is causing problems with e.g. links in emails incorrect.

To use rewrite url routine of the webserver is another.

When creating a new question limesurvey should prefill the code field of the question with 0001 or any other scheme.

Speeds up entering questions if you afterwards regenerate the codes.

If you have "No answer" globally deactivated, you sometimes add an item "No answer" by hand to certain questions.

If you then want to use "other answer", the position of "other answer" is below "No answer".

So it would be a common feature to allow "Other answer" at a certain position in the list.

The most flexible way, would be to allow a "Other answer" field behind every item in the list.

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.