You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In elections with Yes votes, there is a logical error with cumulative votes. It is possible to create an election that allows more votes per option than the maximum number that can be cast. This is incorrect. The maximum vote value is defined independently of cumulation. The accumulation is ranked behind it. It only specifies the maximum number of votes that can be cast per option. This value cannot be higher than the maximum number of votes.
The backend already seems to detect this correctly, as the value of the maximum number of votes that can be cast is taken into account when the votes are cast.
Additionally the button to send votes doesn't become active if numbers are added. It stays gray, but it can be clicked.
Example of ballot setting - affected settings are marked in red:
Example what happened during voting - number is entered, but button is still gray
Example - number entered is to high and the dialog show correctly the maximum possible votes:
How to Reproduce
Steps to reproduce the behavior:
open a meeting
open settings > elections > ballots > mark 'Allow to accumulate several votes on one candidate ("comulative voting")'
open elections > create an election > add a candidate > create a ballot with voting method 'yes per candidate' > add in 'Maximum amount of votes' 4 > add in 'Maximum amount of votes per option' 6 > select in 'entitled to vote' admin group > save
start the ballot and enter a 6 in the number of votes field
Expected behavior
The maximum number of votes per option should be based on the maximum number of votes. 'Maximum amount of votes per option' may be either equal to or less than the value in 'Maximum amount of votes'. If a larger value is entered, an error should appear and it should not be possible to create the vote.
In addition, the voting button should become active as soon as a value has been entered.
The text was updated successfully, but these errors were encountered:
Describe the bug
In elections with Yes votes, there is a logical error with cumulative votes. It is possible to create an election that allows more votes per option than the maximum number that can be cast. This is incorrect. The maximum vote value is defined independently of cumulation. The accumulation is ranked behind it. It only specifies the maximum number of votes that can be cast per option. This value cannot be higher than the maximum number of votes.
The backend already seems to detect this correctly, as the value of the maximum number of votes that can be cast is taken into account when the votes are cast.
Additionally the button to send votes doesn't become active if numbers are added. It stays gray, but it can be clicked.
Example of ballot setting - affected settings are marked in red:
Example what happened during voting - number is entered, but button is still gray
Example - number entered is to high and the dialog show correctly the maximum possible votes:
How to Reproduce
Steps to reproduce the behavior:
Expected behavior
The maximum number of votes per option should be based on the maximum number of votes. 'Maximum amount of votes per option' may be either equal to or less than the value in 'Maximum amount of votes'. If a larger value is entered, an error should appear and it should not be possible to create the vote.
In addition, the voting button should become active as soon as a value has been entered.
The text was updated successfully, but these errors were encountered: