Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a new group restores previous configurations on the units (teams - content groups) #36307

Open
BryanttV opened this issue Feb 26, 2025 · 0 comments

Comments

@BryanttV
Copy link
Contributor

BryanttV commented Feb 26, 2025

Expected Behavior

The unit configuration is maintained independently of the Groups in Teams created.

Actual Behavior

The unit configuration is restored when I create a new Group in Teams.

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. In Studio, create a new Unit, and configure it to Restrict access to some Team.

  7. As a student, join the Team previously configured. You'll be able to see the content.

  8. Now, as staff create a new Group, similar to step 4.

  9. See again the Unit configured; the configuration is missing.

  10. As a student, you'll not be able to see the unit, even if you belong to the initially configured Team. Only the Staff can see the Unit.

content-group-with-teams-bug-1.mp4

Additional Information

Notes

The bug also occurs when using the legacy interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant