Alisha - feature : implementation of BMDashboard grouped bar-graph showing Issues created vs Resolved of projects backend

[alishawalunj]

Description

Related PRs (if any)

This backend PR is related to the #4272 frontend PR.

Main changes explained

• Configured Router to fetch issue trends and summary.
• Configured Controller to implement logic for getIssueSummary and getIssueTrends.
• Configured IssueAnalytics schema to store issues, their status, and dates of resolution and reporting.

How to test

1. Check out the current branch.
2. Run npm install and start the application locally.
3. Clear site data/cache in your browser.
4. Log in as an admin user.
5. Test the following endpoints in Postman:

Without parameters:

• Get Issues Summary:
  http://localhost:4500/api/issues/summary
• Get Issues Trends:
  http://localhost:4500/api/issues/trends

With date range parameters:

• Summary:
  http://localhost:4500/api/issues/summary?start=2025-10-01&end=2025-10-19
• Trends:
  http://localhost:4500/api/issues/trends?start=2025-10-01&end=2025-10-19

With weeks parameter:

• Summary:
  http://localhost:4500/api/issues/summary?weeks=4
• Trends:
  http://localhost:4500/api/issues/trends?weeks=4

Screenshots or videos of changes:

[akshith312]

Tested PR locally.
Logged in as admin user. Tested all endpoints mentioned with params, work as expected.

Get Issues Summary:

Get Issues Trends:

Summary with date range:

Trends with date range:

Summary with weeks:

Trends with weeks:

[Aswin20010]

IssueGraph page functions as expected — filters, tiles, and chart update dynamically. Date range validation works correctly, and the layout aligns with design requirements in both light and dark modes. Implementation is stable and meets feature specifications.

[beblicarl]

i have reviewed the frontend and it worked as intended

OneCommunityGlobal/HighestGoodNetworkApp#4272 (comment)

[sayali-2308]

• Checked out branch: alisha/feature/issue-analytics-grouped-bar-graph
• Frontend branch: alisha/feature/issues-bar-graph
• Tested on: Windows, Postman
• Server running on port 4500

API Endpoints Tested:

1. GET /api/issues/summary

• Response: 200 OK
• Returns correct JSON structure:

  {
    "success": true,
    "data": {
      "totalIssues": 0,
      "newIssues": 0,
      "resolvedIssues": 0,
      "averageResolutionTimeDays": 0
    }
  }

2. GET `/api/issues/trends`
- **Response:** 200 OK
- **Returns correct JSON structure:**
```json
  {
    "success": true,
    "data": [],
    "meta": {
      "startDate": "2025-12-05T05:00:00.000Z",
      "endDate": "2026-01-31T04:59:59.999Z",
      "weeks": 9
    }
  }

3. Tested with query parameters:
- `/api/issues/summary?weeks=4` - Works correctly
- `/api/issues/trends?weeks=4` - Works correctly
- Date range parameters work as expected

Integration:
-  Frontend successfully fetches data from both endpoints
-  No CORS issues
-  No authentication issues
-  Response format matches frontend expectations

[Anusha-Gali]

Hi Alisha,

I have reviewed your PR locally and was able to view the data in the backend which i was not able to verify in the frontend.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud