We use same seed for all order of questions …
We don't have this issue already reported ?
https://github.com/LimeSurvey/LimeSurvey/blob/42cfc2d9c6f7eb0302a8bddefa24d2203cb84339/application/models/Question.php#L796
https://github.com/LimeSurvey/LimeSurvey/blob/42cfc2d9c6f7eb0302a8bddefa24d2203cb84339/application/libraries/MersenneTwister.php#L45

https://forums.limesurvey.org/index.php/forum/design-issues/134562-random-order-is-the-same-for-all-questions#241594

Here is an idea how to fix that: Give every question its own fixed random number that is kept when the survey is exported and imported.
That field could be part of the question table and named 'random_salt'. It is immutable.
Combined with the response's seed value, each question gets its own order. That order stays the same for the participant even if questions are renamed or reordered, or the survey is re-imported from an archive.

The cause: All randomized questions in a response start from the same random value, so questions with the same number of subquestions always end up in the same order. In preview a new value is picked every time, which is why it looks fine there.

Here is an idea how to fix that: Give every question its own fixed random number that is kept when the survey is exported and imported.

I'm sure I add another idea somewhere

It's about a new Question atribute : "Salt for randomization" :

• Empty : qid+seed (or near something like this)
• Set (by expression manager) use it : can be {QCODE.qid}+seed

Then : by default all questions didn't have same order, but you can set the same order for some specific question.

PS : https://bugs.limesurvey.org/view.php?id=18675 seems deleted ?

Forum discussion related : https://forums.limesurvey.org/forum/design-issues/157327-randomising-answers-in-consecutive-multiple-choice-questions?utm_source=chatgpt.com

If you want different randomization, use different sub-question codes.

Having such a solution can really be great !
Adding a "salt" to the seed came from Question attributes can certainly be a good solution.

#18675 is there.

THe QID can change on restoring from an archive and this makes it for usage as salt worthless.
My proposal is better because the stored salt per question will be immutable.
If a user wants to change it, fine with me - show a stern warning, though.

THe QID can change on restoring from an archive and this makes it for usage as salt worthless.

Right, but unsure of the real issue here :)

My proposal is better because the stored salt per question will be immutable.

Then create (and show it in settings) when a question is created?