Dormant User Feature inactivates new users after admin approves
Summary
The dormant user feature on our self-hosted omnibus GitLab EE instance is not working as expected. When a new user would sign up and be approved by and admin they would automatically be flagged as dormant if they did not log in before the next time the dormant user job ran.
Additionally, dormant users needed and admin to reactivate their account, rather than the advertised functionality of Users can reactivate their account by signing in.
It should be noted we also have Require admin approval for new sign-ups
enabled.
Steps to reproduce
- Turn on Require admin approval for new sign-ups at the instance level
- Turn on Dormant users at the instance level
- Have new user sign-up
- Administrator approves user
- Wait until after next time dormant user job runs
- User then tries to log-in for the first time
What is the current bug behavior?
User is marked inactive and requires admin to re-activate them
What is the expected correct behavior?
User should not be inactive until 90 days after their account was created