Page MenuHomePhabricator

Add a new vote-able status that is above "Under review" but before a triaged status
Closed, ResolvedPublicFeature

Description

Problem

Apart from "Under review", the current statuses are all product-related and deterministic of the wishes' future. "Under review" exists as the catch-all before triaging a wish, but user's can't vote on them.

The theory is that if we allow the community to show us how important a wish is to them (by way of voting), it could effect which status the stakeholder chooses. We basically just need a status that's equivalent to "this wish is valid, let's let people vote on it", but isn't yet triaged by WMF or stakeholders.

Acceptance criteria
  • Add a new vote-able status, let's call it "Accepted", that sits in between "Under review" and the others.

The statuses are stored in configuration and have unique numerical IDs. This means "Accepted" will have to come last in the config, and thus in the dropdown in Special:WishlistIntake. If this is deemed problematic, maybe we could alphabetically sort the dropdown options so the ordering doesn't cause confusion.

Event Timeline

'Accepted' sounds good to me.

For sorting, we could add another key to the status' config, called sortKey or whatever, and sort on that. It would be nice if it came next after 'Under review'.

dmaza changed the subtype of this task from "Task" to "Feature Request".Oct 9 2025, 4:50 PM
Samwilson changed the task status from Open to In Progress.Oct 10 2025, 9:23 AM
Samwilson claimed this task.

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

[mediawiki/extensions/CommunityRequests@master] Add 'accepted' status

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

The statuses are stored in configuration and have unique numerical IDs. This means "Accepted" will have to come last in the config

I might be missing something here. Can't we just store them out of numerical order, and they'll display in the order we want? (See the above patch.)

The statuses are stored in configuration and have unique numerical IDs. This means "Accepted" will have to come last in the config

I might be missing something here. Can't we just store them out of numerical order, and they'll display in the order we want? (See the above patch.)

Should be fine if we don't try to sort it ¯\_(ツ)_/¯

Change #1195180 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Add 'accepted' status

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

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

[mediawiki/extensions/CommunityRequests@wmf/1.45.0-wmf.22] Add 'accepted' status

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

Change #1195756 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@wmf/1.45.0-wmf.22] Add 'accepted' status

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

Mentioned in SAL (#wikimedia-operations) [2025-10-13T23:10:49Z] <musikanimal@deploy2002> Started scap sync-world: Backport for [[gerrit:1195756|Add 'accepted' status (T406674)]]

Mentioned in SAL (#wikimedia-operations) [2025-10-13T23:36:04Z] <musikanimal@deploy2002> musikanimal: Backport for [[gerrit:1195756|Add 'accepted' status (T406674)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2025-10-13T23:50:50Z] <musikanimal@deploy2002> Finished scap sync-world: Backport for [[gerrit:1195756|Add 'accepted' status (T406674)]] (duration: 40m 01s)

MusikAnimal changed the task status from In Progress to Open.Oct 14 2025, 6:57 AM

This has already been deployed. It was just a configuration change, so I'm going to do QA the favor and resolve :)