Page MenuHomePhabricator

Deploy watchlist labels
Closed, ResolvedPublic

Description

This involves settting wgEnableWatchlistLabels to true in config and deploying the changes.

The consensus on the team right now is there's reason to do a staggered deployment across different wikis, so unless that changes in the meantime let's deploy everywhere at once (after testwiki).

Event Timeline

Change #1229946 had a related patch set uploaded (by Samwilson; author: Samwilson):

[operations/mediawiki-config@master] Enable watchlist labels on testwiki

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

Change #1229946 merged by jenkins-bot:

[operations/mediawiki-config@master] Enable watchlist labels on testwiki

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

Mentioned in SAL (#wikimedia-operations) [2026-01-26T08:05:40Z] <samwilson@deploy2002> Started scap sync-world: Backport for [[gerrit:1229946|Enable watchlist labels on testwiki (T413967)]]

Mentioned in SAL (#wikimedia-operations) [2026-01-26T08:28:44Z] <samwilson@deploy2002> samwilson: Backport for [[gerrit:1229946|Enable watchlist labels on testwiki (T413967)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2026-01-26T08:43:19Z] <samwilson@deploy2002> Finished scap sync-world: Backport for [[gerrit:1229946|Enable watchlist labels on testwiki (T413967)]] (duration: 37m 38s)

Change #1233651 had a related patch set uploaded (by Samwilson; author: Samwilson):

[operations/mediawiki-config@master] Enable watchlist labels everywhere (prod and beta)

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

Samwilson added subscribers: TheresNoTime, Samwilson.

I've scheduled the deployment for the UTC morning backport window today.

Samwilson changed the task status from Open to In Progress.Mon, Feb 2, 1:13 AM

Change #1233651 merged by jenkins-bot:

[operations/mediawiki-config@master] Enable watchlist labels everywhere (prod and beta)

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

Mentioned in SAL (#wikimedia-operations) [2026-02-02T08:04:00Z] <kharlan@deploy2002> Started scap sync-world: Backport for [[gerrit:1233651|Enable watchlist labels everywhere (prod and beta) (T413967)]]

Mentioned in SAL (#wikimedia-operations) [2026-02-02T08:27:21Z] <kharlan@deploy2002> kharlan, samwilson: Backport for [[gerrit:1233651|Enable watchlist labels everywhere (prod and beta) (T413967)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2026-02-02T08:45:46Z] <kharlan@deploy2002> Finished scap sync-world: Backport for [[gerrit:1233651|Enable watchlist labels everywhere (prod and beta) (T413967)]] (duration: 41m 47s)

Well, looks like good things are happening, but they are stuck in the middle or something. Today we get a guided tour on Watchlist labels at Special:Watchlist. Creating new labels works. But the buttons "assign labels" and "remove labels" sometimes appear greyed, and sometimes does not appear without a reason. Is there a chance there are more Gerrit changes to deploy today, maybe? And couldn't find the most important task, at least for me, that adds the labels data to query/list/watchlist entries Action API call. Still, thanks a lot you're working on this.

image.png (590×1 px, 71 KB)
image.png (584×1 px, 56 KB)
image.png (589×1 px, 57 KB)

The greying out of the buttons has already been done away with in favour of popups that explain the states in which the buttons will not do anything (e.g. if you don't first select any pages to apply labels to). Those fixes will go out in tomorrow's train.

As for the buttons not appearing at all, that's because they're front-end only (i.e. Vue components) and so the page's full JS has to load before the buttons will appear. There is not yet a no-JS interface for adding or removing labels.

And thank you for the reminder about the watchlist API; I've created T416154. Please amend as you see fit.

Thank you for your answer.

The greying out of the buttons has already been done away with in favour of popups that explain the states in which the buttons will not do anything (e.g. if you don't first select any pages to apply labels to). Those fixes will go out in tomorrow's train.

So, until then we can't use the new feature at all?

As for the buttons not appearing at all, that's because they're front-end only (i.e. Vue components) and so the page's full JS has to load before the buttons will appear. There is not yet a no-JS interface for adding or removing labels.

You mean if the buttons do not appear at all, I need wait?

And thank you for the reminder about the watchlist API; I've created T416154. Please amend as you see fit.

Exactly, thank you.

So, until then we can't use the new feature at all?

No, you just have to click one or more checkboxes and the disabledment will disappear (or the enabledness will emerge).

You mean if the buttons do not appear at all, I need wait?

Yeah, just make sure the page has completely finished loading. If it has, and they still don't appear, then that might be a bug. But it sounds like you're getting this intermittently, is that right? Like the buttons load sometimes and sometimes they don't?

So, until then we can't use the new feature at all?

No, you just have to click one or more checkboxes and the disabledment will disappear (or the enabledness will emerge).

Well, sometimes that do not emerge with many chcekboxes.

You mean if the buttons do not appear at all, I need wait?

Yeah, just make sure the page has completely finished loading. If it has, and they still don't appear, then that might be a bug. But it sounds like you're getting this intermittently, is that right? Like the buttons load sometimes and sometimes they don't?

Well, sometimes they do not appear after minutes.

And btw, I just thought about it, could be nice to add a "set this label to that page in my watchlist API".

Well, sometimes that do not emerge with many chcekboxes.
Well, sometimes they do not appear after minutes.

If this annoying behaviour persists, could you please open a new bug report? Thanks!

set this label to that page in my watchlist API

That'll be done in T416291.

Well, sometimes that do not emerge with many chcekboxes.
Well, sometimes they do not appear after minutes.

If this annoying behaviour persists, could you please open a new bug report? Thanks!

Very well, but I'm not sure how much I will use them until T416154 is resolved.

set this label to that page in my watchlist API

That'll be done in T416291.

Thank you.

One more idea for you. Add a single label optional parameter to setnotificationstamp Action API, alongside with entirewatchlist parameter. Hope you consider it. Thank you.

I'm not sure I understand, why would it be better to set labels via action=setnotificationtimestamp rather than action=watch? But if you think it's a good idea, then feel free to open a task for it! (We should keep this one about the deployment.)

I'm not sure I understand, why would it be better to set labels via action=setnotificationtimestamp rather than action=watch? But if you think it's a good idea, then feel free to open a task for it! (We should keep this one about the deployment.)

No. Not instead action=watch. That one adds label to a page. I'm talking about a need to mark all the pages with a particular label as seen, for example. Or reset them to unseen state as it was a week ago.

And also this. Maybe there is a chance you could help me with using the Watchlist labels on the Patch Demo, so I can start working on my own code? I asked it in the proper place, but looks like that user is busy for now. And if you can answer, it will be great.

No. Not instead action=watch. That one adds label to a page. I'm talking about a need to mark all the pages with a particular label as seen, for example. Or reset them to unseen state as it was a week ago.

Makes sense! I've created T417357.

Maybe there is a chance you could help me with using the Watchlist labels on the Patch Demo, so I can start working on my own code? I asked it in the proper place, but looks like that user is busy for now. And if you can answer, it will be great.

I've created T417358 and left a comment on your patch.

I think everything is done here, and that as the Quality Serivces team are busy with other things I think we can bypass QA.