-
Notifications
You must be signed in to change notification settings - Fork 79
[Feature]: directly delete poll without archiving it first #3564
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
Comments
The archive is used instead of deleting by intention, to get the archived polls out of the view (like a trash bin). Otherwise we need a more obvious deletion state and an undelete option to save people by accidentially deletions. At least a threshold can be defined to remove old archived polls by cron job. |
OK. The archive cleaning threshold seems just to be developed in my imagination. 😆 |
Thanks for the prompt feedback!
They still get loaded, affecting the app performance, and it sounds better from the user experience to achieve the desired result with 1-2 clicks. It's complicated for an end-user to even find a delete function, if they're not aware poll needs to be archived first.
That is usually well handled with confirmation dialog (see updated mockups in description) to prevent accidental deletions |
I was happy to eliminate most confirmation dialogs. Anyway. At the moment I am dealing with the vue migration in a local branch. Until this will be finished new features or changes should be avoided. |
Signed-off-by: dartcafe <github@dartcafe.de>
Describe the goal you'd like to achieve
When a user wants to delete a poll, it must be archived first. In a second step, the poll can be deleted.
As a feature request, a direct Action Button to delete a poll would be nice-to-have in the list of polls using the "three-dots menu" (where now only "Duplicate poll" and "Archive poll" option can be found)
This way, it would be much easier for users to delete polls which are not needed anymore.
Describe possible solutions
Additional context
No response
The text was updated successfully, but these errors were encountered: