The templates aren’t creative or consistent, they should be updated to look more modern with a new colour scheme. Possibly making it easier to edit templates too.

If we need to present some group to specific token, maybe in some order, or if we need to present some answer in specific order for some people, it's very difficult to do in javascript.

Randomization of questions is a great feature included in LimeSurvey 1.91. For people using LimeSurvey in psychological research, however, knowing the order in which randomized trials are presented can be important. In the analysis of psychological data, trial number is often included as an additional variable, to account for learning or fatigue effects.

I am experiencing the same issue with twodifferent kinds of question:
1) I have set up a multiple numerical input question so that the people who decide to answer must distribute 100 points (%) into a few categories (equals_num_value = 100). This question is set up as not mandatory. However when one decides to skip it and go on, a warning saying that the question must be properly answered appears. In this way it is not possible to go on without answering this question, which is what I don't want. I would like people to be free to answer or not this question. Those who decide to answer must answer properly, that is they must distribute 100 points into given categories;
2) the same thing happens in a ranking question. The question is not mandatory: so the people who decide to answer must rank all the listed categories (7), while those who decide to skip it must have the chance to go on without answering.

To make the initial stucturing of a survey faster, it would be very helpful to be able to import a mindmap as the basic survey structure.

Level 1 Branches would be sections, level two answers. We could even go so far as to design standardised icons to identify the question types. The text attachment to a node would serves as the description of the question...

What do you think?

J

For the next version it's could be great if limesurvey support Sqlite3.

This 'little' DBMS file system est very simple and could answer for a lot of users of limesurvey.

By this way it's very easy to have various samples.

The assessment options in Limesurvey are currently reasonably limited, and a personality type assessment would be useful.

The type of survey I'm trying to build at the moment is a personality survey where a user goes through a number of questions, and based on the totals of their answers to options A, B or C, their personality trait can be identified.

eg Based on the percentage of A, B and C a particular trait might be highlighted. This trait would be then displayed to the survey participant, as well as being recorded as the result of the survey along with the answers and assessment score ideally.

> 50% A = Type X
> 50% B = Type Y
> 50% C = Type Z
> 40% A & > 40% B = Type XY
> 40% B & > 40% C = Type YZ
> 40% A & > 40% C = Type XZ
> 30% A & > 30% B & > 30% C = Type XYZ

In some circumstances it's quite difficult to statically configure the endURL of a survey.

An example of this is when hosting the survey in a portlet as part of a portal container. Portlet render URLs tend to be quite complex in construction and it's certainly inadvisable (and quite difficult) to construct them statically.

Every now and then we find incomplete surveys.
The user might get bored in the middle (happens usually for long surveys) and/or close his browser window (can be sometimes unexpectedly ) which results in incomplete survey.

In 1.92, there are a lot of new tip ( EM validation etc ..)

Maybe we ca have multi solution for hide_tip option:

0 : allways show ( default)
1 : hide in css and show if error ( actual no)
2 : completely remove tip ( even in HTML)

Because, maybe there are some user who don't want tip, but want use help text like a tip :).

LS 1.9 allows copying specific conditions from one question to one or more other questions.

Would like to be able to do the reverse of this, namely choose a condition in one question and remove that condition from selected other questions.

Well, would be great to give someone data entry level access to limesurvey in order to complete surveys manually.

Many shared hosting providers have an hourly limit on how many emails you can send out.

To manage this limit, you have to babysit LimeSurvey and press the button in batches.

If you exceed the hourly limit, bunches of emails will not go out and often you will receive bounced email messages. It is a mess to determine who did get your invitation / reminder and who did not.

Use of the #answerNNXNNXNN id means code must be updated for all questions that are re-used, in order to re-target form elements. This is tedious, error prone, and frustrating.

The solution proposed does not suggest removing the #id, but adding an alternative for scripting targetting.

In response to suggestions regarding my forum post #33698, I am requesting the following feature:

I would like to see an attribute for the short free text question type textbox for entering a password. Instead of seeing the password, the user would see a character such as a "dot" or an asterisk.

Thank you!

I can't see why the user has to enter ID manually when creating question groups or questions. There should be an option letting LS auto generate IDs which the user can override if needed.

There are some survey results needed to be handle as soon as posible. For example, sales leads or dissatisfied customer feedback. If customers took the survey and willing to leave their personal information for sales contact, system should send the notification email to admin as soon as possible. Sometimes in customer satisfication survey need this alert also. If system can send alert email when customer click dissatisfied rating, agents can handle their complain immediately.

The idea is to develop a tree view like windows explorer with nodes to navigate more faster between Group, questions and subquestions

The idea is: during answering respondent could change his vote, think different time on each question, swich to other window or site (this data names paradata - data about collection of information). It is important to record all this movement and actions to further analise.

It would be nice if the Question Validation Equation is only used when the user navigates past the question with the Question Validation Equation.

If you, for example, use a Question Validation Equation in the third question of your survey and the participant answers the first question the third question will be shown in red if you don't check whether it is null or not.

The situation is that the person didn't even try to answer the question because he/she is at a question before. But I think it would make sense to use/check the Question Validation Equation only if the person is working with the question.