Skip to content

fix: Resolve 500 error in metrics and complete dashboard

Edouard Legoupil requested to merge feature/add-new-metrics-and-visualizations into main_dev

Created by: Edouard-Legoupil

This commit resolves a 500 internal server error on the /api/metrics/development-time endpoint and completes the implementation of the metrics dashboard.

Backend changes (backend/api/metrics.py):

  • Reverts the get_development_time_metrics endpoint to its original, self-contained implementation to resolve the incompatibility with the refactored filter helper.
  • Corrects the query construction in the get_cycle_time_metrics endpoint to ensure the WHERE clause is correctly formatted.

Frontend changes (frontend/src/screens/Dashboard/components/MetricsDashboard/MetricsDashboard.jsx):

  • Replaces all 'coming soon' placeholders with actual charts for 'Proposals by Category' and 'Donor Interest'.

  • Implements useMemo for chart data processing to improve performance.

  • Adds new visualizations for 'Average Funding Amount' and 'Proposal Volume'.

  • 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