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

Polls/elections: problem with default value analog #3008

Closed
MSoeb opened this issue Nov 13, 2023 · 1 comment · Fixed by #3009
Closed

Polls/elections: problem with default value analog #3008

MSoeb opened this issue Nov 13, 2023 · 1 comment · Fixed by #3009
Assignees
Labels
bug critical Highest priority: This has to be done first.
Milestone

Comments

@MSoeb
Copy link

MSoeb commented Nov 13, 2023

Description: If a user changes the default value of voting type for polls or elections to analog in the settings, votes didn't work anymore. (Also an error message appears in the console.) Even if the value is switched back to other voting types, it's not possible to reactivate the voting function.

Affected setting - voting type of ballots (elections)
Screenshot_20231113_121059

Affected setting - voting type of motions
Screenshot_20231113_121129

error message during vote creation - motions
Screenshot_20231113_121243

error message during ballot creation:
Screenshot_20231113_121313

Reproduction:

  1. open a meeting
  2. open settings > motions > default voting type > change to analog
  3. open settings > elections > default voting type > change to analog
  4. open motions > create a motion > change status to a state were voting is possible > create a vote
  5. open elections > create a new election > add candidates > create a new ballot
  6. Try to switch back the default voting type for motions and perform step again -> won't work -> voting is not possible anymore

What should happen:
Changing default voting types for elections and/or motions to analog shouldn't lead to a fatal error of the whole voting system.

@MSoeb MSoeb added bug critical Highest priority: This has to be done first. labels Nov 13, 2023
@MSoeb MSoeb added this to the 4.1 milestone Nov 13, 2023
@bastianjoel bastianjoel self-assigned this Nov 13, 2023
@bastianjoel
Copy link
Member

Regression from #2963

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug critical Highest priority: This has to be done first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants