Skip to content

feat: Redesign dashboard and apply multiple bug fixes

Edouard Legoupil requested to merge redesign-dashboard-and-fix-bugs into main_dev

Created by: Edouard-Legoupil

This commit introduces a complete redesign of the dashboard UI and fixes several bugs identified during development.

Features:

  • The dashboard has been completely redesigned to match the provided wireframe, including new tabs, project cards with status badges and icons, a search bar, and a filter modal.
  • The MultiSelectModal component has been made more generic to support dynamic titles and confirmation actions.
  • Font Awesome has been added to support the new icons in the UI.

Bug Fixes:

  • A TypeError in the document generation backend (/api/generate-document) is resolved by correctly handling pre-parsed JSON data.

  • The peer review modal in the chat screen now displays the correct title ("Select Users for Peer Review") instead of the generic "Select Outcomes".

  • A crash in the dashboard when viewing the "Pending Reviews" tab has been fixed. This was addressed by:

    1. Updating the /proposals/reviews backend endpoint to include the form_data object in the response.
    2. Making the frontend Project.jsx component more robust by using optional chaining (?.) to safely access form_data properties, preventing crashes if the data is missing.

  • 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