Change Details

In order to increase the number of editors that interact with the Revise Tone Structured Task during the A/B test, we should put one of it at the front of the queue of tasks on the Homepage (and Post-Edit panel?). Putting a Revise Tone task first in the Post-Edit panel is a nice-to-have. If it is not much effort to add that, then that would be great to do. But the focus is the Homepage, so if this would take a lot of additional effort, then let's skip it. This should be temporary scaffolding. We do not plan to keep this functionality after the A/B test is over. **Acceptance Criteria:** * [ ] if a user has the Revise Tone task type selected, and we have Revise Tone suggestions available for their selected topics, then we should put a Revise Tone task at the front of the queue of tasks that they see on the homepage * [ ] if a user is in the control group (does not have the Revise Tone task), and we have Copyedit suggestions available for their selected topics, then we should put a Copyedit task at the front of the queue of tasks that they see on the homepage To limit the scope and complexity, we need only focus on logic that impacts the Homepage upon loading. We do not need to consider changing the post-edit panel logic. ~~* [ ] (TBD) similarly, a Revise Tone task should also be at the front of the queue on the post-edit panel~~

In order to increase the number of editors that interact with the Revise Tone Structured Task during the A/B test, we should put one of it at the front of the queue of tasks on the Homepage. This should be temporary scaffolding. We do not plan to keep this functionality after the A/B test is over. **Acceptance Criteria:** * [ ] if a user has the Revise Tone task type selected, and we have Revise Tone suggestions available for their selected topics, then we should put a Revise Tone task at the front of the queue of tasks that they see on the homepage **Notes:** * To limit the scope and complexity, we only focus on the logic that impacts the Homepage upon loading. We do not need to consider changing the post-edit panel logic, nor the logic for loading a new set of tasks when the user edits their topics or task types. * Also, the experience for the control group should be unchanged.

In order to increase the number of editors that interact with the Revise Tone Structured Task during the A/B test, we should put one of it at the front of the queue of tasks on the Homepage (and Post-Edit panel?). Putting a Revise Tone task first in the Post-Edit panel is a nice-to-have. If it is not much effort to add that, then that would be great to do. But the focus is the Homepage, so if this would take a lot of additional effort, then let's skip it. This should be temporary scaffolding. We do not plan to keep this functionality after the A/B test is over. **Acceptance Criteria:** * [ ] if a user has the Revise Tone task type selected, and we have Revise Tone suggestions available for their selected topics, then we should put a Revise Tone task at the front of the queue of tasks that they see on the homepage * [ ] if a user is in the control group (does not have the Revise Tone task), and we have Copyedit suggestions available for their selected topics*Notes:** * To limit the scope and complexity, then we should put a Copyedit task at the front of the queue of tasks that they see on the homepage To limit the scope and complexitywe only focus on the logic that impacts the Homepage upon loading. We do not need to consider changing the post-edit panel logic, we need only focus on logic that impacts the Homepage upon loading. We do not need to consider changing the post-edit panel logic. ~~* [ ] (TBD) similarlynor the logic for loading a new set of tasks when the user edits their topics or task types. * Also, a Revise Tone task should also be atthe experience for the front of the queue on the post-edit panel~~control group should be unchanged.