Account changes fix

[Zasa-san]

PR checklist:

• [ ] Update READ.me ?
• [ ] Update API documentation ?

QA checklist:

• [ ] Smoke test the functionality described in the issue
• [ ] Test for side effects
• [ ] UI responsiveness
• [ ] Cross browser testing
• [ ] Code review

[Zasa-san]

When the password is not valid, the side panel is closed, and it is necessary to open it again to continue the action, in the case of creating a user the form remains dirty, the edition however is reseting the values. It would be great, if it is possible to keep the side panel opened after the error, with the dirty fields for both cases.

That's a good point. I will leave the sidepanel open when the password is incorrect. That way the user will not loose changes.

Reset Password doesn't ask for the confirmation password, as I think it was agreed by the team, however, there is a pre existent validation error while applying the action on many users.

If you are testing this with our e2e fixtures that happens because one of the users (editor) doesn't have an email. That's not possible to archive without manually manipulating the DB and removing the user email, since you can't create a user without an email.

The email field is also reset after a password error.

Will fix!

typos on submmitedPassword and worngPass

Thanks for the catch :eye:

@mfacar