Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Admin des Besoins): Demande de modification ou clôture d'un besoin #1596

Open
wants to merge 35 commits into
base: master
Choose a base branch
from

Conversation

chloend
Copy link
Contributor

@chloend chloend commented Dec 17, 2024

DDB = dépôt(s) de besoin

Quoi ?

Permettre de demander des modifications sur un DDB ou de le clôturer si nécessaire.

Pourquoi ?

Actuellement, les admins sont contraints de mettre une mention "HS" sur le titre des besoins afin de les trier. Cela leur permettra de gagner du temps et d'améliorer le suivi des DDB.

Comment ?

1. Modèle Tender

  • Ajout de l'attribut email_sent_for_modification : un booléen à False par défaut

Ajout de deux méthodes :

  • reset_modification_request : réinitialise les champs email_sent_for_modification et/ou changes_information lorsque des modifications ont été apportées et que le statut du besoin passe de "brouillon" à "publié".
  • set_modification_request : sauvegarde les champs email_sent_for_modification, status et logs après avoir cliqué sur le bouton d'envoi de modification dans l'admin.

2. Modèle Conversation

a. Ajout deux de TemplateTransactional dans une migration :
  • TENDERS_AUTHOR_MODIFICATION_REQUEST : template de mail de demande de modification d'un DDB
  • TENDERS_AUTHOR_REJECT_MESSAGE : template de mail de rejet du DDB

Captures d'écran (optionnel)

  • Capture des besoins avec mention "HS"
  • Capture des besoins avec le champ email_sent_for_modification à True
  • Capture des besoins dont le statut est "rejeté".

Autre (optionnel)

  • À la demande de @SebastienReuiller, j'ai remplacé toutes les références à "@beta.gouv.fr" par "@inclusion.gouv.fr"

@chloend chloend force-pushed the chloend/tender-hs branch 5 times, most recently from dbc29a9 to 3e3e43c Compare December 30, 2024 18:23
@chloend chloend requested a review from Guilouf December 31, 2024 11:48
lemarche/tenders/admin.py Outdated Show resolved Hide resolved
lemarche/www/tenders/tasks.py Outdated Show resolved Hide resolved
lemarche/www/tenders/tasks.py Outdated Show resolved Hide resolved
lemarche/utils/urls.py Outdated Show resolved Hide resolved
lemarche/www/tenders/tasks.py Outdated Show resolved Hide resolved
lemarche/www/tenders/tasks.py Outdated Show resolved Hide resolved
lemarche/tenders/admin.py Outdated Show resolved Hide resolved
@chloend chloend marked this pull request as ready for review January 16, 2025 05:48
@chloend chloend requested review from Guilouf and madjid-asa January 16, 2025 05:48
Copy link
Contributor

@SebastienReuiller SebastienReuiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super fonctionnalité, bravo !
Je t'ai fait quelques retours ;)

lemarche/api/tenders/views.py Outdated Show resolved Hide resolved
lemarche/www/tenders/tasks.py Outdated Show resolved Hide resolved
lemarche/tenders/admin.py Outdated Show resolved Hide resolved
Copy link
Collaborator

@Guilouf Guilouf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image
Lorsque la demande à été rejetée, elle est toujours listée parmi les demandes de l'acheteur, mais rien n'indique qu'elle a été rejetée. Il faudrait faire pareil quel lorsqu'elle est cloturée, ex:
image

clevercloud/tenders_update_status_to_rejected.sh Outdated Show resolved Hide resolved
@SebastienReuiller
Copy link
Contributor

Merci @Guilouf .

J'ai ajouté le badge "Rejeté" sur le dashboard :
image

Sur la liste :
image

Et sur le détail :
image

J'ai aussi ajouté des tests.

lemarche/static/js/favorite_item.js Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_esat_from_asp.py Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_esat_from_asp.py Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_esat_from_csv.py Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_esat_gesat.py Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_esat_handeco.py Dismissed Show dismissed Hide dismissed
lemarche/siaes/management/commands/import_sep.py Dismissed Show dismissed Hide dismissed
lemarche/www/auth/views.py Dismissed Show dismissed Hide dismissed
lemarche/www/siaes/views.py Dismissed Show dismissed Hide dismissed
lemarche/www/siaes/views.py Dismissed Show dismissed Hide dismissed
@SebastienReuiller
Copy link
Contributor

J'ai également corrigé le chevauchement sur le lien. Merci @Guilouf pour ta vigilance.

Avant:

image

Après:

image

@gip-inclusion gip-inclusion deleted a comment from gitguardian bot Feb 5, 2025
Copy link

gitguardian bot commented Feb 7, 2025

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@SebastienReuiller
Copy link
Contributor

Nouveau message dans la liste:
image

Onglet et message pour les rejetés:
image

Copy link
Collaborator

@Guilouf Guilouf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ca me parait nickel, merci pour tes corrections !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants