You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First Open edX Named Release Without This Functionality
Ulmo
Rationale
It doesn't look like ENABLE_COMPLETION_TRACKING_SWITCH support was built into the MFE outline or navigation pages, meaning that the main thing it gates is the recording of completion data, not the display of completion to the learner. That means that users just get a broken experience when this is switched off, where they see things are incomplete but have no way to mark them completed.
changed the title [-][DEPR]: ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/-][+][DEPR]: Remove ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/+]on May 20, 2025
[inform] This DEPR is in the Draft state. It can't move forward without a DEPR coordinator to help update it to match the updated DEPR template. No action is required, unless anyone wants to move this out of Draft.
@feanil: This ticket originally followed the old flow, so I don't believe this was announced. Basically, this DEPR is making completion mandatory vs optional, as originally designed. This is all probably fine, but we still want DEPRs to go through the process to enable and inform (and possible feedback). And we should probably update the description to match the current template. Thanks.
Since this is only adding capability and not breaking anything, I think we can treat this as a fast-track DEPR. We just need to do the cleanup at this point.
Activity
[-][DEPR]: ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/-][+][DEPR]: Remove ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/+]robrap commentedon May 23, 2025
[inform] This DEPR is in the Draft state. It can't move forward without a DEPR coordinator to help update it to match the updated DEPR template. No action is required, unless anyone wants to move this out of Draft.
feanil commentedon Jun 25, 2026
Fastracking this because without this, the functionality is broken
robrap commentedon Jun 29, 2026
@feanil: This ticket originally followed the old flow, so I don't believe this was announced. Basically, this DEPR is making completion mandatory vs optional, as originally designed. This is all probably fine, but we still want DEPRs to go through the process to enable and inform (and possible feedback). And we should probably update the description to match the current template. Thanks.
feanil commentedon Aug 12, 2026
Since this is only adding capability and not breaking anything, I think we can treat this as a fast-track DEPR. We just need to do the cleanup at this point.
feanil commentedon Aug 12, 2026
Looks like work has already begun via #444