@Insertcleverphrasehere: Adding PageTriage project tag so this task can be found when looking at PageCuration tasks at https://phabricator.wikimedia.org/tag/mediawiki-extensions-pagecuration/ . No need to add team tags like Growth-Team; that is up to each team (or automatic filters).

It appears the CommTech team is working on this.

@Niharika We might want to take this off the Sprint board until it's ready :)

@Niharika In the code, there was some previous functionality were if the article was marked as Reviewed the message was sent to the reviewer. I could see this behavior now that I'm always displaying the message box. Just to clarify, when the button says "Mark as Unreviewed" the message is also meant to be sent to the creator?

We discussed this in the meeting. Here's a summary:

• The Review/Unreview and Send a message workflows should be completely decoupled.
• The Send a message box is always there and the message is always sent to the creator
• Unreviewing an article sends an automated message to the prior reviewer (This functionality remains unchanged)

Change 519578 had a related patch set uploaded (by HMonroy; owner: HMonroy):
[mediawiki/extensions/PageTriage@master] Separate mark as review/unreview and send message to page creator workflows

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

@HMonroy After checking out your patch, when I click the "Mark as reviewed" button it becomes disabled and there is a little spinner, but nothing happens (in the UI) after this to indicate the action has been successful (which it has).

It stays like this.

In T207442#5292321, @dom_walden wrote:

@HMonroy After checking out your patch, when I click the "Mark as reviewed" button it becomes disabled and there is a little spinner, but nothing happens (in the UI) after this to indicate the action has been successful (which it has).

It stays like this.

@dom_walden I was able to replicate this, I've submitted the fix for review. Thank you!

Change 519578 merged by jenkins-bot:
[mediawiki/extensions/PageTriage@master] Separate mark as review/unreview and send message to page creator workflows

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

• When user hits Mark as reviewed, that only marks the page as reviewed and does not send message to creator.

"Review" and "Unreview" function as they do previously (as recorded in Special:Log and status of Green/Grey tab).

@Insertcleverphrasehere @ifried It should be noted that, when Unreviewing, it is no longer possible to add a custom message for the previous reviewer. Is this ok?

It just posts a generic message to the previous reviewer (e.g. https://en.wikipedia.org/wiki/Template:Unreviewednonote-NPF).

• Add a new button Send message to creator which sends a message to the page creator if there is text present in the textarea. The button is disabled if there is no text.

It is still possible to send a message to the creator's User_talk page.

The template it uses now is {{subst:Sentnote-NPF|..., which I see is not on en.wiki (it would be https://en.wikipedia.org/wiki/Template:Sentnote-NPF). @Insertcleverphrasehere @ifried Who needs to know in order for this to be created?

An example of what it puts on a user's talk page:

{{subst:Sentnote-NPF|1=Page Title|2=Reviewer Username|3=Message for creator}}

• Position the elements according the mockup above (with a horizontal separator between the two different steps.

It looks as it does in the screenshot in the description above :)

• The checkmark on the tab turns green only if the page has been marked as reviewed (no relation to whether a message was sent to creator).

Turns green appropriate to reviewed/unreviewed status.

Unreviewing someone else's review is a strong act that has caused conflict in the past. The inability to send a message noting why is less than great in my thinking.

Hey there, I'm posting some general updates on this ticket (see below):

Request for Templates

For this new update to work, we’re requesting that the community adds the following template: Sentnote-NPF. This template is already being called in the code, so we’ll need it added in order for the new custom message template (sent to page authors) to be available.

Customized Message Clarification

This work required that we decouple two sections that were previously tied together: a) “mark as reviewed,” b) send a message to the creator process. When these two sections were tied together, they would adapt to one another. For example, if one reviewer unreviewed someone else’s work, the message would be sent to the reviewer (which would display on the user’s talk page). Otherwise, the default behavior was to send a message to the page creator.

Now that we have decoupled these two functions, the process is different. The message section is now meant to notify the page creator. The message is also posted to article talk page. Meanwhile, if someone unreviews someone’s work, a general message (i.e. not customizable) will be sent to the previous reviewer’s user talk page. This message is only sent if the current reviewer is different than the previous reviewer. To be clear, the user can still manually write a customized message directly on the talk page (this will just not be possible via the messaging tool, as we’ve decoupled the processes).

In short, this change occurred because we needed to decouple the two functions, and we needed to do it in a streamlined way (as we’re balancing many projects and requests). Would this cause a significant issue for reviewers?

Pinging @Barkeep49 and @Insertcleverphrasehere, so they can chime in regarding the two points mentioned in my previous message. Thanks!

@ifried I have not been active this week so apologize for the slow response. Separating out the functions is no issue that I can foresee. Making a template should be rather straight forward too. What's the name of the template that the toolbar calls now to leave a message? Changing that to work for Sentnote-NPF seems like it should be straight forward.

@Barkeep49 Thanks for your response and flexibility regarding the changes! The template toolbar is now calling Sentnote-NPF, so if the community updates the template, the changes should then be available. In that case, the community can let me know (on Phabricator, Wikipedia, or meta) when the template has been updated, and then I can resolve this ticket. Thanks!

So far kupdung is the only one who has expressed an opinion. I asked you a question at WT:NPR. Pending your answer I'll suggest a template and if no one objects within a day or two will implement it.

@Barkeep49 Thanks for the update. I just responded to the question on WT:NPR. I hope that I sufficiently answered the question -- but, if I did not, I'm happy to elaborate. In that case, I'll wait for an update regarding implementation of the template or any other questions posed by the community.

Template:Sentnote-NPF now exists and I think this is ready to go live - sorry for the delay. Work continues to be busier than normal and so I've not had as much Wikipedia time as usual.

Thanks, @Barkeep49, for the update. In that case, the changes should all be live and ready to test. Can you let us know if these changes are working as expected on production, when you get a chance? Thank you!

@ifried So the sending the note without reviewing works properly, so yeah. Am I correct that there is no way to both review and send a note?

@Barkeep49 Thanks for verifying. Yes, the processes have been completely decoupled, so each action (i.e. reviewing and sending a note) would need to be triggered separately. I'm marking this work as resolved, as we've now verified the behavior (as described in the requirements) on production. Thanks!

In T207442#5419094, @ifried wrote:

@Barkeep49 Thanks for verifying. Yes, the processes have been completely decoupled, so each action (i.e. reviewing and sending a note) would need to be triggered separately. I'm marking this work as resolved, as we've now verified the behavior (as described in the requirements) on production. Thanks!

Maybe we could also decouple the addition of tags? T148353 and T221514 are use cases

@DannyS712 The Community Tech team is currently only focusing on Page Curation updates that were part of the 2019 Community Wishlist. However, if you're interested in further Page Curation improvements, requests can be forwarded to the Growth team (which typically manages Page Curation) or canvassed for the 2020 Community Wishlist. Thanks!