openedx / openedx/frontend-app-authoring

Enabling content groups for teams breaks the content groups functionality (teams - content groups)

Open
#1,698 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
17
Forks
218
Avg merge
9d 20h
Merged PRs (30d)
20

Description

Expected Behavior

Content groups for Teams and Content groups with Cohorts should work correctly.

Actual Behavior

Content groups for Teams don't allow the creation of new Content Groups with Cohorts.

Steps to Reproduce

  1. Create a Waffle Flag for your course in {lms_domain}/admin/waffle_utils/waffleflagcourseoverridemodel/

    • Waffle Flag: teams.content_groups_for_teams
    • Course id: [Your Course ID]
    • Enabled: ✅
  2. Enables Teams in the platform using the teams.enable_teams_app flag.

  3. Enable teams for your course in Studio > [Your Course] > Content > Pages & Resources > Teams > Teams toggle

  4. In the same modal of Configure teams, create a few Groups.

  5. Then, go to the LMS > [Your Course] > Teams and create a few Teams within those Groups (Topics/team-sets)

  6. From Studio, go to Settings > Group Configurations.

  7. There are 3 unexpected behaviors:

    • Does not show all configured Teams.
    • Show the Edit and Delete buttons for the Team Groups, although these are not modifiable from here.
    • Content Groups can't be created.

https://github.com/user-attachments/assets/34d0f5ff-7432-4878-88ad-0a52f167e165

Additional Information

Currently, the functionality works correctly with the legacy interface. To use the legacy interface, disable the contentstore.new_studio_mfe.use_new_group_configurations_page waffle flag.

https://github.com/user-attachments/assets/85e7f93e-6d4e-415e-8021-cb8c5fc93226

Contributor guide

Open the 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.

Research direction

Start by reproducing the issue in Studio > Settings > Group Configurations with teams.content_groups_for_teams, teams.enable_teams_app, and contentstore.new_studio_mfe.use_new_group_configurations_page enabled. Compare the new page with the legacy interface; done means all configured Teams appear, Team Groups lack Edit and Delete controls, and Content Groups can be created with Cohorts.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.