Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When editing a quiz the 'Question order' value is always displayed as 'Randomized' #12248

Closed
rtibbles opened this issue Jun 5, 2024 · 3 comments · Fixed by #12278
Closed
Assignees
Labels
TAG: user strings Application text that gets translated TODO: needs decisions Design or specifications are necessary

Comments

@rtibbles
Copy link
Member

rtibbles commented Jun 5, 2024

When editing a quiz the 'Question order' value is always displayed as 'Randomized'. Note that it's not clear what should happen if I have both sections with randomized and fixed order:

Question.order.mp4

Originally posted by @pcenov in #12232 (comment)

@rtibbles rtibbles added TODO: needs decisions Design or specifications are necessary TAG: user strings Application text that gets translated labels Jun 5, 2024
@Tweniee
Copy link
Contributor

Tweniee commented Jun 6, 2024

more info

@LianaHarris360
Copy link
Member

Hi @Tweniee, there are still some decisions that need to be made before work on this issue can begin. The issues open for contributors have a help wanted label, you can take a look at some of those unassigned issues here.

@rtibbles rtibbles self-assigned this Jun 6, 2024
@rtibbles
Copy link
Member Author

rtibbles commented Jun 6, 2024

In discussion with @nucleogenesis - it seems that this top level randomize property should now actually be for the order of the sections, so the copy needs to be updated to reflect that at a minimum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TAG: user strings Application text that gets translated TODO: needs decisions Design or specifications are necessary
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants