Skip to content

feat/US756-manage-last-duel

Marlène SIMONDANT requested to merge feat/US756-manage-last-duel into dev

What does this MR do and why?

Lorsque le dernier défi a été réalisé (Maria Sharapowatt) on cherche à prévenir l'utilisateur qu'il n'y a pas d'autres défis et on l'invite à nous écrire.

Cf maquettes : https://www.figma.com/file/MiXXGdDuiSNmuSbZAavVTz/LLLE-Mobile?node-id=12656%3A82656

Pop-up à afficher à la fin du défi Sharapowatt (une fois uniquement)

Puis dans le tableau des médailles à suite des différentes cards afficher la card https://www.figma.com/file/MiXXGdDuiSNmuSbZAavVTz/LLLE-Mobile?node-id=12656%3A82849

Le bouton "suggérer une idée..." renvoie vers la bulle jaune (ou vers le SAU partie "Idée" si mis en place)

Screenshots or screen recordings

image

image

How to set up and validate locally (or on alpha)

Pour arriver au dernier duel du dernier challenge, modifier les dates des duels dans la base...

MR acceptance checklist

To be completed by the chosen reviewer.

Quality

  • Confirmed
  1. 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.
  2. I have made sure that the sonar quality coverage is up to standards.
  3. I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
  4. I have tested this MR in all supported browsers or determined that this testing is not needed.
  5. 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
  1. I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
  2. I have considered the scalability risk based on future predicted growth.

Documentation

  • Confirmed
  1. I have prepared a squash commit to feed the changelog linked to the current milestone.
  2. 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
  1. I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.

Deployment

  • Confirmed
  1. 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.
Edited by Marlène SIMONDANT

Merge request reports