Change #1198309 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] [DNM][WIP] PoC: ensure a task of a given type id is returned first

https://gerrit.wikimedia.org/r/1198309

Change #1200110 had a related patch set uploaded (by Michael Große; author: Michael Große):

[mediawiki/extensions/GrowthExperiments@master] feat(ReviseTone): on homepage, promote ReviseTone or Copyedit tasks

https://gerrit.wikimedia.org/r/1200110

I've updated the description based on the decision to not change the experience for the control group. (See internal conversation)

Change #1200110 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat(ReviseTone): on homepage, promote ReviseTone tasks

https://gerrit.wikimedia.org/r/1200110

QA Note: This should be testable beta-enwiki: usually, when having multiple tasks selected on the homepage, it will be random which shows first. But now, if Revise Tone is also selected, then when reloading the homepage a Revise Tone task will always show up first.

Change #1198309 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] ReviseTone: A/B test experiment setup

https://gerrit.wikimedia.org/r/1198309

QA observation:
I'm not able to select a revise tone task type on mobile or desktop. Not sure if it's because I need to self enrol into the experiment or the fact that I'm not in the treatment group.

I have tried logging in and out again but I'm not getting the Revise Tone task type.

I am no longer blocked after @Sgs shared with me a way to add myself to the treatment group. I can now see the Revise Tone task

I'm not seeing any article suggestions when I select the Revise Tone option. Let me know if there's something else I need to enable.

This appears to coincide with the fact that we don't have articles matching hasrecommendation:tone in the search

I created a new account which was added to the treatment group and this does indeed show the revise tone task as the first task regardless of it's initial position in the api pages array.

This works on Mobile and Desktop.

Meets Acceptance Criteria: ✅

I need to confirm whether a user who selects revise tone, unselects it, then reselects it again, is still meant to have revise tone as the first suggestion? I noted that this wasn't the case when I followed that pattern. Reloading the page seems to fix this and set the revise tone as the first task.

In T407528#11388227, @DMburugu wrote:

I need to confirm whether a user who selects revise tone, unselects it, then reselects it again, is still meant to have revise tone as the first suggestion? I noted that this wasn't the case when I followed that pattern. Reloading the page seems to fix this and set the revise tone as the first task.

No, this was deemed not necessary, as it happens only very rarely. It will only be on the front when the homepage freshly loads, either from navigating to it or from a refresh in the browser.

Thanks for the clarity. We can mark this as passing QA.