feat(profile): structure owners screen
|
---|
What does this MR do and why?
Afficher l'écran de modification des membres : https://grandlyon.icescrum.com/p/RESIN/#/taskBoard/222/story/2261
|
---|
Screenshots or screen recordings
How to set up and validate locally (or on alpha)
- Se connecter
- Aller dans "Voir mon compte"
- Dans le menu d'une structure, cliquer sur "Gérer les membres"
- Tester l'ajout d'un user existant dans Resin et d'un user non existant dans Resin
- Tester d'exclure un user existant dans Resin et un user non existant dans Resin
MR acceptance checklist
To be completed by the chosen reviewer.
-
Quality-
Confirmed
- For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
- I have made sure that the sonar quality coverage is up to standards.
- I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
- I have tested this MR in all supported browsers or determined that this testing is not needed.
- I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.
Performance, reliability and availability
-
Confirmed
- I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
- I have considered the scalability risk based on future predicted growth.
Documentation
-
Confirmed
- The MR is named after the desired squash commit to feed the changelog linked to the current milestone.
- I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.
Security
-
Confirmed
- I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.
Deployment
-
Confirmed
- When featured on a self-data project release, i have made sure my app version in the manifest and package.json is incremented and any relative changes to the permissions are clearly written and transmitted to Cozy.