Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

reviewGrades and manageSubmissions rosters don't filter by role

Open Beginner friendly
#364 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, python
Domain
frontend

Research direction

Start with frontend/src/pages/reviewGrades/index.js and frontend/src/pages/manageSubmissions/index.js, then trace how get_course_enrollment and the course roles are provided to those pages. Make both rosters exclude other TAs and co-instructors while retaining students; done when staff no longer appear in either roster.

Written by the indexing model from the issue text.

Description

get_course_enrollment returns all enrolled users regardless of role. Neither frontend/src/pages/reviewGrades/index.js (which only excludes the current viewer: allRes.filter(s => s.id !== userInfo.id)) nor frontend/src/pages/manageSubmissions/index.js (no filtering at all) excludes other TAs or co-instructors from the roster they display. If a TA or a second instructor is enrolled in a course and has ever had a Submission row (e.g. via future staff-testing, see #363), they'd currently show up alongside real students in grade review and submission management.

This is independent of whether staff-testing (#363) ever ships — it's a pre-existing gap in role filtering on these two pages today.

Found while investigating a review comment from Cecilia (yczhangcc) on PR #355.

Dominant language
Python
Stars
13
Forks
0
Avg merge
2h 4m
Merged PRs (30d)
1

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kiat/codeAssist

All issues in kiat/codeAssist

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.