Skip to content

[DEPR]: Remove ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch #370

Open

Description

@ormsbee

Proposal Date

2025-05-20

Ticket Acceptance Date

2025-06-04

Technology Removal Date

2025-07-04

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.

Removal

This would require removing the switch's use in edx-platform, as well as the removal of it from the completion repo itself.

Replacement

No replacement. The behavior would be as if it was permanently switched on today.

Deprecation

No response

Migration

No response

Additional Info

Turning this switch has been the default for Tutor installation since October of 2020.

Activity

  1. added
    deprProposal for deprecation & removal per OEP-21
    on May 20, 2025
  2. changed the title [-][DEPR]: ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/-] [+][DEPR]: Remove ENABLE_COMPLETION_TRACKING_SWITCH Waffle Switch[/+] on May 20, 2025
  3. self-assigned this
    on May 20, 2025
  4. robrap commented on May 23, 2025

    @robrap
    Contributor

    [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.

  5. added theissue type on Jan 28, 2026
  6. moved this from Draft to Plan Accepted in DEPR: Deprecation & Removalon Jun 25, 2026
  7. feanil commented on Jun 25, 2026

    @feanil
    Contributor

    Fastracking this because without this, the functionality is broken

  8. moved this from Plan Accepted to Breaking Changes Unblocked in DEPR: Deprecation & Removalon Jun 25, 2026
  9. robrap commented on Jun 29, 2026

    @robrap
    Contributor

    @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.

  10. feanil commented on Aug 12, 2026

    @feanil
    Contributor

    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.

  11. feanil commented on Aug 12, 2026

    @feanil
    Contributor

    Looks like work has already begun via #444

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

deprProposal for deprecation & removal per OEP-21good first issueA good task for a newcomer to start withhelp wantedReady to be picked up by anyone in the community

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions