In some situation where you have to "replay" many times the same filters sets on various surveys (but with same question set) it can be very long and bothering to click each time on hundreds of filter sets.

It would be great if questions containing subquestions (e.g. array questions with multiple questions) could display in statistics and graphs together on a single chart.

Also, pie charts are a poor way to display data that is not categorical in nature. Ordinal (e.g. education level) or scale (e.g. age) variables are hard to make sense of in pie charts.

For example, I often ask respondents to agree or disagree with a number of related statements. It would be good to view the responses together and displayed in a way that conveys that the responses are on a continuum.

Hi,

it would be helpful for comparability of the statistical graphs by using consequently the same colour for first, second, third … answer even if there is no answer given on one choice. For example there are some questions of type 5 point choice array. On one question nobody gives the answer “1”. Now you look at your graphs of the statistic and in all pie-charts you see blue=”1”, red=”2”, green=”3”, yellow=”4” and olive=”5” only in the one, where no one selected the first choice “1” blue stands for “2”, red for “3” and so on. To compare the charts it would be better to skip the colour where the statistical answers are null.

The statistics view is not as easy to theme / style as the rest of the survey.

into the lime_surveys table there is a field datecreated when the survey was created. What I would like to know about a survey is when it was activated. this to create statistics about how long the surveys are running(or have ran) on our system.

ofcourse to determin how long a survey has ran there would also be a need for DateLastDeactivated.

It would be nice to show the running time of a survey on the current statistics pages. And as in our case those fields could be used for custom statistics about all the surveys that are currently running on the system.

use case

The creator of a survey should be able to include a lottery into the survey. The participant will leave his/her e-mail address for participation in the lottery. In the admin tool it should be possible to see how many people have participated in the lottery and randomly select a number of e-mail addresses for the winners.

requirements

- If the participant takes part in the survey no conclusions about the participant should be possible. For example if the e-mail address is stored in the same survey database table or the sessionID and timestamp of the participation of the survey and lottery are stored in both of the two separate tables.
- The lottery should be part of a survey. It should not be a link to a new/additional survey (with navigation and "submit" button).
- The selection of winners should be done automatically by the LimeSurvey admin tool.

I run quite a few surveys that are open for 7 days. It is important to issue reminders, and it is important to do this with the right timing, and it would be good to keep other people in our own organizations, and in the customer organization up to speed with the way the survey is going - most specifically with regards to the response rate.

For a company using Limesurvey to do market research type of inquiries this would be an easy way to get an edge vs some of the more expensive non-open source tools that exist.

I had the idea that this should be possible to do using an rss feed. The RSS feed should provide data for;

The name of the survey
When the invitations were sent out
Number of respondents that have been invited
Number of completed surveys

So for example;
Survey [SURVEYNAME]
Started [DATE, TIME]
Invited number of respondents [RESPONDENTS_INVITED]
Completed number of surveys [COMPLETED_SURVEYS] corresponding to a
response rate of ([COMPLETED_SURVEYS]/[RESPONDENTS_INVITED]) %.

The evaluated TOTAL assessment (sum) is nicely displayed at the end of the survey - which can only be seen by the user who filled the survey in.
However, this result is not stored at the answers database. After a lot of user filled the survey in, i would like to see the sums given for all of these users.
Now i have to export the answers and should repeat the assessment / summarize in Excel before i can see these TOTAL sums.

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.

We need to disseminate survey results to a large amount of people, and creating users/group and access permissions, plus training everyone to be able to pull result data etc is not practical.

The ability to show text responses and export them from the statistics page would solve this problem and allow quick dissemination of qualitative and qualitative data in an easy to use, familiar format (PDF/Excel)

I run many surveys for many different companies on a Limesurvey account. What I would like to be able to offer them is:

real-time access to their survey results displayed in a dynamic interface, like a proper reporting tool. This would complete the delivery from Limesurvey, from start/invitations, through the survey runtime all the way to reporting the results.

Up to now (LS 1.87) there are no statistics for question type "date" available. It would be nice to create some charts (showing results in a table isn't necessary from my point of view) so the admin gets an overview which date was entered.

My survey has list comments questionnaire but I am unable to see the comments when I generate the stats in PDF or Excel. For report consolidation purposes, I think it will be extremely helpful to be abel to see the comments typed by respondents even in the PDF and Excel format.

Actually survey users either have press the next button after each questions or after filled out the complete number of questions belonging to questions group.

The first option is often tiring, while the second on may result in very large / long input screens.

The options of creating small question groups is not always convenient as they normally correspond to a logical unit (for which e.g. you want to keep or provide an assessment score).

Majority of the times people we use survey to generate statistics across multiple projects.
If I have the same questions asked to same people on different projects and present the data collected on multiple surveys collectively.
Can we have this feature in which we can have reporting on a global basis which is applicable to all the projects.

I would like a function like spss split file and select cases in the ouput function. This would make it possible to compare different groups and easily make a quick report of a sub population.

There should be an ability to set a quota for total complete or incomplete responses to a number
After the quota has been reached the survey could be expired

If you want to show statistic on-line page to client you could send him a link to public statistic, but this link can be guessed by anybody who knows LimeSurvey script....

When viewing survey results of questions which use INSERTANS placeholders these placeholders are displayed within the question text at the answer overview. When using lots of INSERTANS placeholders within one question the overview is hard to read (see screenshot) because of the additonal text/strings.

It would be nice if these placeholder were filtered.

An example can be found at http://bugs.limesurvey.org/view.php?id=3508

We use the limesurvey as a survey for our mystery shoppers, it works well, but we wonder why we receive complains from some of them from time to time that an interruption occurs while filling a survey, a problem that doesn't happen frequently, but it happens sometimes and leads to loss of time and effort!

I suggest that you add a logging system, so that we may be able to trace users steps on our surveys, this way, we may recognize the source of the problems! it's maybe a bug in a browser or an action that the user takes by fault, logging system would help us in finding these facts and by consequent recommend tools to users to avoid these problems rather than fixing them!