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

No way to reassign a course to another instructor

Open
#388 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
backend

Research direction

The issue describes disabled instructor removal and the lack of course management in the admin panel, but names no files, tests, or entry points. First read the discussions in #312, #378, and #380 to understand the constraints; work cannot be scoped until the product decision among the listed options is made.

Written by the indexing model from the issue text.

Description

An admin can't remove an instructor who is teaching any course. The Remove Instructor button is disabled until those courses are gone (added in #312 so courses don't end up without an owner).

Since #378 removed course management from the admin panel, an admin also has no way to move a course to a different instructor. In practice, removing an instructor who has courses now requires the instructor to delete their own courses first, which deletes the course data too. That doesn't work if the instructor has left, or if the course should continue under someone else.

Options:

  1. Add a narrow admin-only "change instructor" action for a course, without giving admins any other course access.
  2. Let an instructor hand a course over to another instructor or TA themselves.
  3. Leave it as is and handle it manually in the database when it comes up.

This is a product decision. Option 1 keeps admin power limited to accounts and ownership, which matches the reasoning in #380.

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.