Steps to Repro (Bug 1):
- Log into folio (I used https://bugfest.folio.ebsco.com)
- Go to Users and pick an active user with an empty expiration date or one in the future
- Edit the user
- Select status = inactive
Expected: Status change should save.
Actual: Status stays active.
Steps to Repro (Bug 2):
- Log into folio
- Go to Users and pick an active user with an expiration date in the future
- Edit the user
- Remove the expiration date
Expected: Status should remain Active
Actual: Status changes to Inactive. It is possible to edit the user record and change the status back to Active, but there is no reason for it to automatically inactivate because the expiration date was removed.
- The original intention (and function) of this feature was that the status menu was editable so status could be manually changed to inactive for reasons other than user expiration. Additionally, when the expiration date had passed, the status would automatically change to inactive and the menu would become uneditable. You'd then have to edit the expiration date (push it out or remove it) to be able to reset the status to active. See
UIU-235for details (there is a lot more detail in the comments, as well).
- This feature also interacts with FOLIO login. If a user has 5 failed login attempts they will be set to inactive. In this case, it is possible to manually re-set the user to active. See
UXPROD-28and UIU-513for more details on this feature.
Discuss with developers: What is the best path forward for this?
- Try to return things to the way they were working before or redesign to make this less brittle?
- One possible alternative/interim fix is defined in
- Should we create a separate field for "Login blocked" so we aren't trying to do two things with the status menu?