Page MenuHomePhabricator

Confirm beta opt-in and (graduated) New Filters opt-out are compatible
Closed, ResolvedPublic

Description

T168376 describes a mechanism for opting out of the New Filters UX (once the UX graduates out of beta on RC page). The New Filters beta, however, covers more than just RC page, since it also includes beta features that are (or will be) on Watchlist. We need to confirm that these two preferences are compatible with one another, in the following ways:

Users who opt IN to the beta but OUT of the graduated UX on RC page

After RC page graduation, New Filters beta opt-in users who select the "Hide the improved version of Recent Changes" preference will have the following experience:

  • They will get the old UX on RC page. They will see NO new features (as described in T168376).
    • The same holds true for Related Changes, which we are generally treating as a flavor of RC page.
  • These users will, however, continue to get all beta features on Watchlist.
  • (Selecting the "Hide the improved version of Recent Changes" option expresses no preference about a future version of Watchlist that has also graduated out of beta. When that happens, we will create a new opt-out for Watchlist.)

lf whoever takes this task confirms that the functionality currently is as above, we can close the task. If it's not, however, we should figure out what needs to be done and rewrite the task.

Related Objects

Event Timeline

I just approved the patch for T168376 and confirmed it works with that patch. I can opt into the beta feature but out of the RC page, and when I do that I get the old interface on the RC page and the new interface on the watchlist.

Checked in betalabs - opting out via "Hide the improved version of Recent Changes" option provides all old functionality for RC page and RelatedChanges page. Watchlist filters are controlled with the current beta features.

Note (not related to this ticket) : It's still highly confusing that some of the functionality is controlled from Preferences-RecentChanges and some from Preferences-Watchlist but affects both pages.

  • "Group changes by page in recent changes and watchlist" is placed only on Preference-RecentChanges
  • Prediction threshold which affects both RC and Watchlist is placed only on Preferences-Watchlist

QA Recommendation: Resolve

jmatazzoni closed this task as Resolved.Sep 14 2017, 7:33 PM
jmatazzoni claimed this task.

Checked in betalabs - opting out via "Hide the improved version of Recent Changes" option provides all old functionality for RC page and RelatedChanges page. Watchlist filters are controlled with the current beta features.
Note (not related to this ticket) : It's still highly confusing that some of the functionality is controlled from Preferences-RecentChanges and some from Preferences-Watchlist but affects both pages.

  • "Group changes by page in recent changes and watchlist" is placed only on Preference-RecentChanges
  • Prediction threshold which affects both RC and Watchlist is placed only on Preferences-Watchlist

Thanks Elena. You are right. This kind of thing is exactly why we worked thought the Preferences Consolidation tickets (T172350 etc.), and why we should do these them.