Skip to content

Manusha Job Posting Page Analytics: Create a donut chart showing applicants by experience - #1457

Open
manushajyasta30 wants to merge 2503 commits into
Manusha_donut_chart_show_applicants_by_experiencefrom
development
Open

manushajyasta30 wants to merge 2503 commits into
Manusha_donut_chart_show_applicants_by_experiencefrom
development

Conversation

@manushajyasta30

Copy link
Copy Markdown
Contributor

Description

image

Related PRS (if any):

T
To test this backend PR you need to checkout the ##3654 frontend PR.
…

Main changes explained:

added routes:
Route: GET /api/applicants/experience-breakdown
GET http://localhost:4500/api/experience-breakdown?roles=Frontend Developer
GET http://localhost:4500/api/experience-breakdown?startDate=2023-01-01&endDate=2024-12-31
…

How to test:

  1. check into current branch
  2. do npm install and ... to run this PR locally
  3. Clear site data/cache
  4. log as admin user
  5. verify endpoints

Screenshots or videos of changes:

image

@manushajyasta30 manushajyasta30 changed the title Job Posting Page Analytics: Create a donut chart showing applicants by experience Manusha Job Posting Page Analytics: Create a donut chart showing applicants by experience Jun 14, 2025
@one-community one-community added the High Priority - Please Review First This is an important PR we'd like to get merged as soon as possible label Jun 18, 2025
@Venk-rgb Venk-rgb self-assigned this Jun 19, 2025
smartha-del and others added 30 commits September 4, 2026 19:35
The "+ Add New" column had only a per reviewer read, so a table showing it
for a page of reviewers made one request, and one query, per row. This adds
the bulk read promised to the frontend on 09-01:

  POST /api/promotion-eligibility/pr-entries  { requestor, reviewerIds: [...] }
  -> { reviewers: { "<id>": { weeks: [...] } } }

Every id sent comes back as a key, including reviewers with nothing listed,
so the client never has to tell "no entries" apart from "id missing from the
response". The per reviewer value is the identical shape the single reviewer
route returns, so only the read location changes on the client.

One query for the whole batch, ids deduplicated first. The single reviewer
route stays, since it is still the better one to hit right after an add or a
rating change when only one row needs refreshing.

13 tests covering the keying, the empty reviewer, week ordering, the single
query, deduplication, the validation cases and the 403 and 500 paths.
…ummary_stats

Ansh - fix Total Org Summary badge stats aggregation
…jury-Trend-Chart

Purav taking over: create injury trend chart
…s-Zero

Gayatri -Fix taskHours always returning 0 in getTaskAndProjectStats
…e-styling-for-ApplicantVolunteerRatio-chart-backend

HANDIKA: update wrong import for applicant volunteer ratio router
…otion-eligibility-dashboard-backend

Sitaram - PRs Needed bands, reviewer groups, weekly requirements, History, PR ratings and Process Promotions
…q_endpoint

Aditya - Job Application Listing Page: allow public read access to the FAQ list
…_BSTimeOff

Revert "Diya 🔥 fix(timeOff): Fixed BS emails for timeoff"
Co-authored-by: Nathan Hoffman <nathanahoffman@gmail.com>
…bility-bug-fix

Ruthwik fix the share availability bug for events
…Create-permission-to-see-and-interact-with-the-deadline-tracking-details

Roshini Seelamsetty: Create permission to see and interact with the deadline tracking details
…nnaire-Profile-ID

Bosu - fix: expose user profile id in HGN questionnaire responses
…leted_date_filter

Akshay Fix Task Completed chart date filtering
PR #2325 added a viewAndInteractWithTaskDeadlinesBoxes permission check to
updateTaskStatus (PUT /task/updateStatus/:taskId). That endpoint is what the
Review button uses to submit a task for review, not the deadline boxes, so
every role without the new permission (Volunteer, Core Team, Manager, Mentor)
got a 403 and the frontend showed "Failed to update task".

Remove the check from updateTaskStatus. The permission itself stays defined
and is still used by the frontend to gate the deadline boxes UI.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ted-hours-be

Gayatri - fix: count hours from volunteers deactivated later in period
…ommitted-hours-be

Gayatri -fix: add committed hours stats to total org summary
…view-permission-403

Sitaram: 🔥 'Failed to update task' when submitting a task for review (403 from updateStatus)
…-extension

Roshini Seelamsetty : Implement permissions logic for task extension count visibility

This branch was successfully deployed

1 active deployment
Production — b0872580 Deployed Oct 11, 2026 by one-community via deploy #1257
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Do Not Review Do not review or look at code without full context Needs New Developer This is a PR that is partially developed but needs someone new to take it over and finish it.

Projects

None yet

Development

Successfully merging this pull request may close these issues.