openedx / openedx/openedx-platform
Group Community TA is added even though there are no divided discussions configured
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Expected behavior
When adding a community TA to a course without cohorts and divided discussions enabled through the membership tab in the instructor dashboard, the Instructor should see an error, and the user shouldn't be assigned with role community TA.
Actual behavior
The error is displayed as expected, however:
- User isn't shown in the community TA section in Membership, but it's seen in the discussions that user has Community TA status.
- The user is added as Community TA to discussions
- It isn't possible to revoke access until the divided discussions functionality is enabled for a course.
Steps to reproduce
- Setup discussions in the course without enabling
Divide discussions by cohortsoption - Try to add user as Community TA on the Membership tab in the Instructor dashboard
- Check discussions post by the assigned user
Additional information
After the Cohorts are enabled for the course and Divide discussions by cohorts option is enabled in discussions, the user appears in the list of Community TA
This issue was reported as part of the redwood testing process: https://github.com/openedx/wg-build-test-release/issues/373
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Membership-tab flow for adding a Community TA when cohorts and divided discussions are disabled, then trace how the assignment is reflected in discussions. Done means the failed operation leaves no Community TA role or discussion access, and access can be revoked without first enabling divided discussions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100