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

Delete participations of long inactive users #2176

Open
janno42 opened this issue May 6, 2024 · 0 comments · May be fixed by #2329
Open

Delete participations of long inactive users #2176

janno42 opened this issue May 6, 2024 · 0 comments · May be fixed by #2329
Assignees
Labels
[C] Backend Focuses on backend implementation [P] Medium Medium priority [S] Easy This issue is self-contained and does not touch too many parts. Good choice for beginners.

Comments

@janno42
Copy link
Member

janno42 commented May 6, 2024

When performing a bulk update of users, the participations of long inactive users should be deleted.
Long inactive users are users who are inactive (or can_be_marked_inactive_by_manager) after the bulk update, and where the last vote_end_date of the user's participations is more than a certain number of months ago. This number should be configurable in the settings as PARTICIPATION_DELETION_AFTER_INACTIVE_MONTHS, with 18 as default.

The bulk update test message should list all users whose participations will be deleted, along with their participation counts.

@janno42 janno42 added [C] Backend Focuses on backend implementation [P] Medium Medium priority [S] Easy This issue is self-contained and does not touch too many parts. Good choice for beginners. labels May 6, 2024
@Redflashx12 Redflashx12 linked a pull request Nov 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Backend Focuses on backend implementation [P] Medium Medium priority [S] Easy This issue is self-contained and does not touch too many parts. Good choice for beginners.
Development

Successfully merging a pull request may close this issue.

2 participants