Tics (aka tic marks) should be visible under the slider bar.

See this sketch: http://img38.imageshack.us/img38/5295/10403feb10095848.gif

benefits: easy read, make it clear it's a slider with discrete values, catch where the handle is in respect to left and right limits.

Details:
type = multiple numerical input
options:
use slider layout = 1
slider min = 0
slider max = 10
slider accurancy = 1

It's more productive to show and review all conditions in a admin page.
Mantain them from there (Edit, add, delete) is considered a plus.

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.

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.

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.

SAS is a powerful statistics application that's pretty broadly used. LimeSurvey already supports exporting results to R and SPSS, which are good packages, but many of our users prefer to use SAS.

We'd like to see support for exporting LimeSurvey data into a format SAS can use, as has been done for SPSS and R.

When chosing a question from the dropdown list at the admin panel you get some information about
- code
- question text
- quesdtion type
- label set
- mandatory?

What's missing is information about assigned question attributes. You always have to switch to the "edit question" screen to get information about assigned question attributes.

This is not very user friendly and a design problem which probably could be fixed easily.

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.