Do you mean I should submit a bug report for this?

I'm proposing that submitting a bugreport first and discussion in the forum afterwards would be a lot better. Even if the bugreport was a misunderstanding, the developers get a signal about the misunderstanding (better UX/Documentation might be the result of a bugreport without bug).

What we see here is a 9 month old thread with no link to a bugreport.
Perhaps there is a bugreport and it wasn't linked here.

Everybody should try to post a bugreport first and then post a thread here in the forum.

I was going to submit a bug report for my initial issue but when I went to replicate it on the latest version of lime, it could not be replicated due to further bugs related to group randomization also reported above. I was swamped at the time so I left it at that and never did come back to this.

Even if the bugreport was a misunderstanding, the developers get a signal about the misunderstanding (better UX/Documentation might be the result of a bugreport without bug).

Do you really think that anyone will track this and register it for the bigger picture? I'd rather say it gets marked as fixed/will not be fixed/closed and then that is it.

I've reported this as a bug:

bugs.limesurvey.org/view.php?id=14965

holch wrote: Do you really think that anyone will track this and register it for the bigger picture?

If you need to close the same bugticket every week, you will get it hammered into your brain. It's pure magic. No need for complex tracking.

I still have my doubts. Closing a bug ticket should be quick and easy, thinking about what could the actual underlying problem be is a lot harder...