Bug #7861
manage: entity field is disabled and readonly, but considered when looking for required field
100%
Description
In the management interface I had a user that was not attached to an entity, I was trying to change one of the attributes but couldn't submit the form as there was no entity, and the entiy field was marked disabled and readonly, so I couldn't even select the default entity.
Associated revisions
manager: remove disabledness of the entity field in user creation form for superusers (fixes #7861)
It also fixes usability problems for administrator of one or many entities.
manager: improve test on user creations (#7861)
History
#1 Updated by Frédéric Péters over 4 years ago
Worse, for an user that had entity set to the default entity, the form would not validate either, as the entity was not submitted (because the select was disabled).
#2 Updated by Benjamin Dauvergne over 4 years ago
- Assignee set to Benjamin Dauvergne
I think the rules for adding/editing an user should be:
| User status \ Number of entities | 1 | many |
| superuser | Can add/edit an user with or without an entity (entity field not required) | |
| administrator of users in 1 entity | New/Edited user is automatically in the only visible entity, entity field is read-only | |
| administrator of users in many entities | Cannot happen | administrator must select one entity in the one he administrates |
I'll define test cases following these rules.
#3 Updated by Benjamin Dauvergne over 4 years ago
- % Done changed from 0 to 100
- Status changed from Nouveau to Résolu (à déployer)
Appliqué par commit authentic2|7cd1455acfba0b5ae02638c0699351b238f2dd69.
#4 Updated by Benjamin Dauvergne over 4 years ago
- Target version set to 2.2.0
#5 Updated by Benjamin Dauvergne almost 4 years ago
- Status changed from Résolu (à déployer) to Solution déployée
#6 Updated by Benjamin Dauvergne about 2 years ago
- Status changed from Solution déployée to Fermé