[DEPR]: Legacy instructor dashboard

[holaontiveros]

RFC Start Date

2026-04-23

Target Plan Accepted Date

2026-05-07

Target Transition Unblocked Date

2026-09-23 (pending completion of CCX dashboard MFE page)

Earliest Breaking Changes Unblocked Date

2026-10-23 (pending completion of CCX dashboard MFE page + Willow code cut)

The legacy CCX instructor dash page is currently IFramed in to MFE experience. That means that operators can transition to the MFE now, but we can't break the underlying legacy CCX dashboard code until the MFE is replaced with a native MFE experience.

Earliest Open edX Named Release with Breaking Changes

Verawood - 2026-04

Xylon - 2027-04

Rationale

The new instructor dashboard is nearly in all place. Is is the default experience for all instructor dashboard functionality except CCX the dashboard. Once the CCX dash is complete, the legacy instructor dashboard will be redundant.

Removal

openedx-platform/lms/djangoapps/instructor/views/instructor_dashboard.py

Line 147 in c3d0c17

sections = []

The implementation for the old instructor dashboard view + related code + related tests, related tests will have the DEPR-38432 number tagged in a comment

Replacement

Link to the new instructor dashboard:

https://github.com/openedx/frontend-app-instructor-dashboard

Deprecation

All code that was found while working on enabling the instructor dashboard redirection by default was marked with the "DEPR-XXXX" tag so it's easily identifiable.

Additional Info

Users that need to revert to the legacy dashboard can enable the following waffle flag:

instructor.legacy_instructor_dashboard

Transition Unblocked Tasks

No response

Feature Removal Tasks

No response

[sarina]

Thanks @holaontiveros - be sure you follow the announcement procedures too in https://docs.openedx.org/projects/openedx-proposals/en/latest/processes/oep-0021-proc-deprecation.html

[pdpinch]

It seems like we're seeing breaking changes as 2026-05-05 despite the earliest breaking changes date being 2026-06-25.

[sarina]

Just noting that I've asked @arbrandes to follow up with @pdpinch on this.

[feanil]

@holaontiveros can we update the ticket with more up-to-date data? The dash is ready to go? When are we planning on dropping the old code?

[feanil]

My understanding is that a CCX related view is currently iframed into the MFE and so we need to port that to APIs + full react frontend and that this feature needs to be backported to Verawood before we can start dropping the legacy instructor dash.

Does that sound right?

[diana-villalvazo-wgu]

Hi @feanil CCX is not iframed, for now when you click on the CCX tab it redirects to legacy UI (not MFE), and yeah we still need the work for CCX, but as far as i remember it will land on Willow, we haven't started working on CCX implementation yet. But we can Depr instructor Dash on Willow and CCX on next one? or should be everything on the same release? 🤔

[feanil]

Thanks @diana-villalvazo-wgu sounds like we'll need to keep the legacy instructor dash code around through willow so that once we introduce the replacement CCX tab, we can still grant folks a fallback for a release. So we'll want to wait till after Willow is cut to cleanup the legacy instructor dash code. Sound right?