Skip to content

feat: Implement Contribution ID and simplified workflow

Edouard Legoupil requested to merge feat-contribution-id-workflow into main_dev

Created by: Edouard-Legoupil

This commit introduces a new, simplified proposal workflow with the statuses: draft, in_review, pre_submission, and submitted.

Key changes:

  • The proposal status enum in the database has been updated to reflect the new workflow.

  • A contribution_id column has been added to the proposals table.

  • A new endpoint POST /proposals/{proposal_id}/save-contribution-id has been added to save the contribution_id.

  • The load_draft endpoint now returns the contribution_id.

  • The frontend UI in Chat.jsx has been updated to reflect the new workflow and to include an input field for the contribution_id when a proposal is in the submitted state.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports