[DEPR]: Divided (cohorted) discussions management on the legacy instructor dashboard
Maintainer thường phản hồi trong vòng 1 ngày
@feanil đang làm issue này rồi.
Từ ngày 11/8/2026.
Đánh giá
Issue này chưa được đánh giá.
Mô tả
RFC Start Date
2026-07-31
Target Plan Accepted Date
2026-08-14
Target Transition Unblocked Date
2026-08-14
Earliest Breaking Changes Unblocked Date
2026-08-14 - Since we're dropping the feature with no replacement, breaking changes are unblocked immediately.
Earliest Open edX Named Release with Breaking Changes
Willow - 2026-10
Rationale
The redesigned frontend-app-instructor-dashboard is replacing the legacy instructor dashboard, and its "Discussions" management section configured divided discussions. Two of the capabilities it offered have no counterpart in the new MFE: dividing discussions by enrollment track, and selectively choosing which topics are divided. The discovery openedx/frontend-app-instructor-dashboard#225 put the question - rebuild these in the MFE or drop them - and this DEPR was how we gauged interest. There was not sufficient interest in keeping them, so they're being removed rather than ported.
Cohort-based division stays. Dividing discussions by cohort remains a supported feature and is configured through the Pages & Resources discussions settings (authoring), so this DEPR must preserve it. Only enrollment-track division and per-topic division selection go away.
The legacy config surface is removed by the legacy-instructor-dashboard DEPR openedx/openedx-platform#38432: the dashboard's "Discussions" management section, its Backbone UI, and the two staff-only config endpoints (course_discussions_settings_handler, discussion_topics) that exist only to serve it all come out together there.
This DEPR covers the remaining backend part: dropping the enrollment-track and per-topic-selection behavior and migrating existing data, while leaving cohort division working. It's a behavior change plus a data migration, so it's kept as its own follow-up and does not block removing the legacy dashboard or the legacy forum tab.
Divided discussions lets staff partition discussion topics so a learner only sees posts from peers in their same cohort or enrollment track. It's configured per course and does nothing unless a course explicitly sets a division scheme (CourseDiscussionSettings.division_scheme defaults to none), so I expect relatively few courses use the parts being removed - though I don't have hard usage numbers.
If you rely on dividing discussions by enrollment track, or on choosing specific topics to divide, please chime in on this ticket.
Removal
The two divided-discussions capabilities being dropped - division by enrollment track and selective per-topic division - and the data and logic specific to them (paths against openedx/openedx-platform master 1746666137). Cohort-based division is preserved throughout.
- Remove the enrollment-track division scheme: the
enrollment_trackoption inCourseDiscussionSettings.division_scheme/available_division_schemes, and the enforcement that divides topics by enrollment track. - Remove selective per-topic division: the ability to choose which course-wide and inline topics are divided (
divided_discussions,always_divide_inline_discussions). Exact field handling has to keep cohort division working - confirm in implementation whether these fields are removed outright or retained to serve the cohort scheme. - A data migration that unsets enrollment-track schemes and per-topic division selections on existing courses, leaving cohort-based division intact.
Preserve: division_scheme == cohort and the topic-division enforcement it drives, since cohort division remains supported and is configured via Pages & Resources.
The legacy management UI (dashboard section + Backbone UI) and the two config endpoints are not in this DEPR - they are all removed by #38432. This ticket is the follow-up that removes the enrollment-track and per-topic behavior once that lands.
Replacement
None for the parts being removed - enrollment-track division and per-topic division selection are dropped, not migrated. Cohort-based division is unaffected and stays configured through the Pages & Resources discussions settings. The new frontend-app-instructor-dashboard covers cohort management (creating cohorts, assigning learners) via /api/cohorts/, which is a separate feature.
Deprecation
Mark the enrollment_track division scheme and the per-topic division fields (divided_discussions, always_divide_inline_discussions) as deprecated, and log a DeprecatedFeatureWarning-style notice where enrollment-track or per-topic division is applied. Leave the cohort scheme unmarked.
Additional Info
Scope split (2026-09): this DEPR originally covered the whole divided-discussions surface. The legacy UI and its config endpoints were moved into the legacy-instructor-dashboard DEPR openedx/openedx-platform#38432 (the dashboard section, its Backbone UI, and the course_discussions_settings_handler + discussion_topics endpoints that exist only to serve it), so they can be cleaned up now and unblock that effort. This ticket handles only the backend removal of the dropped capabilities (enrollment-track + per-topic division) as a later follow-up.
Related: openedx/frontend-app-instructor-dashboard#225 (discovery that surfaced this gap and recorded the decision); openedx/openedx-platform#38936 (MFE/legacy inventory).
- Ngôn ngữ chính
- Python
- Star
- 8.2k
- Fork
- 4.4k
- Merge trung bình
- 2 ngày 10 giờ
- Pull request đã merge (30 ngày)
- 40
Chuẩn bị môi trường
- Không có Dockerfile hay tệp Docker Compose
- Có mẫu pull request
- Đọc hướng dẫn đóng góp
Bắt đầu từ đâu
- Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
- Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
- Fork repository và làm thay đổi trên một nhánh.
- Mở pull request có tham chiếu số hiệu của issue.
Issue khác của openedx/openedx-platform
-
Discussion API: missing thread returns 500 (ForumV2RequestError not mapped to ThreadNotFoundError)Có thể làm lại được @mbhavu2007-lang đã nhận 17 ngày trước và không có pull request nào đang mở. Đang mở
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 72/100
openedx/openedx-platform#39225 · 1 bình luận ·
Maintainer thường phản hồi trong vòng 1 ngày
-
v3 notification preferences: PUT with email_cadence but no notification_channel raises KeyError (500)Có thể làm lại được Pull request cho issue này đã bị đóng mà không được merge. Đang mởbug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 66/100
openedx/openedx-platform#39221 · 1 bình luận ·
Maintainer thường phản hồi trong vòng 1 ngày
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 86/100
openedx/openedx-platform#39169 · 1 bình luận ·
Maintainer thường phản hồi trong vòng 1 ngày
-
bug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 82/100
openedx/openedx-platform#39084 ·
Maintainer thường phản hồi trong vòng 1 ngày
-
Độ khó 2/5 Dưới một giờ Mức phù hợp với người mới 82/100
openedx/openedx-platform#38792 ·
Maintainer thường phản hồi trong vòng 1 ngày
Tất cả issue của openedx/openedx-platform
Issue tương tự
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 82/100
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 78/100
Maintainer thường phản hồi trong vòng 2 ngày
-
Reference check: findingsĐang mởaudit-reference-check
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 78/100
Maintainer thường phản hồi trong vòng 1 ngày
-
screenrec.com stopped workingĐang mởsite-bug triage
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 68/100
Maintainer thường phản hồi trong vòng 1 ngày
-
bug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 77/100
canonical/paas-charm#407 · 1 bình luận ·
Maintainer thường phản hồi trong vòng 5 ngày