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

Meeting archiving: improvement for running process needed #3989

Open
MSoeb opened this issue Aug 9, 2024 · 1 comment
Open

Meeting archiving: improvement for running process needed #3989

MSoeb opened this issue Aug 9, 2024 · 1 comment
Labels
enhancement General enhancement which is neither bug nor feature
Milestone

Comments

@MSoeb
Copy link

MSoeb commented Aug 9, 2024

Current behavior
When archiving meetings, there is no check as to whether there are ongoing processes, such as voting. This leads to practical problems. For example, accounts cannot be merged if they are in an ongoing voting process.

If a meeting is archived, the merge cannot simply be carried out. The current solution is to unarchive the meeting and end the voting. However, this (unarchiving) can only be done by a superadmin. This in turn leads to practical problems, as the superadmin is usually not immediately available.

Wanted behavior
To solve this problem, a check should be carried out during archiving to ensure that there are running processes. This includes votes on motions, elections and active speeches. If one of these processes is active, a dialog box should appear indicating that the following processes are active and should be terminated in order to perform archiving.

@MSoeb MSoeb added the enhancement General enhancement which is neither bug nor feature label Aug 9, 2024
@MSoeb MSoeb added this to the 4.2 milestone Aug 9, 2024
@rrenkert
Copy link
Collaborator

This should be handled in the backend I think. The client still needs to handle the "error" message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement General enhancement which is neither bug nor feature
Projects
None yet
Development

No branches or pull requests

2 participants