Page MenuHomePhabricator

Update the statuses in CommunityRequests
Closed, ResolvedPublic3 Estimated Story Points

Assigned To
Authored By
MusikAnimal
Jul 22 2025, 5:45 PM
Referenced Files
F66327768: 2025-09-23_11-57-19.png
Sep 23 2025, 7:04 PM
F65950174: 2025-09-02_15-10-31.png
Sep 2 2025, 10:15 PM
F65950171: 2025-09-02_15-09-55.png
Sep 2 2025, 10:15 PM
F65950160: 2025-09-02_15-05-59.png
Sep 2 2025, 10:15 PM
F65950155: 2025-09-02_15-05-15.png
Sep 2 2025, 10:15 PM
F65950151: 2025-09-02_15-03-42.png
Sep 2 2025, 10:15 PM
F65950141: 2025-09-02_15-02-10.png
Sep 2 2025, 10:15 PM
F65950133: 2025-09-02_15-01-08.png
Sep 2 2025, 10:15 PM

Description

Problem

Nobody understands wish statuses or focus area statuses

Hypothesis

If we create and socialise a clearer framework for wish statuses, then staff and volunteers will have less confusion about the wishlist.

StatusDescriptionVoting allowed?
Under reviewCommTech maps a new wish to a component and team from the maintainers table.No
UnsupportedUnsupported tools working group reviews these wishesYes
DeclinedWish is misaligned with strategic priorities, a policy matter, or unreasonable.No
Community opportunityWish cannot be fulfilled by WMF but could be done by volunteers.Yes
Long-term opportunityWish is a potential strategic opportunity for 2+ quarters out. Revisit wishes on a quarterly basis to build focus areas.Yes
Near-term opportunityWish is more likely to be adopted within 2 quarters, likely integrated in a focus area or hypothesis.Yes
PrioritizedWish will likely move into “in progress” within the quarterYes
In progressWork is in progress on the wish, or work is inspired by needs articulated in wishYes
DoneWish is fulfilled explicitlyNo

The descriptions are here just to document what each status is. We may later add them as tooltips to the status chip, but for now we're only talking about changing the available statuses (the $wgCommunityRequestsStatuses configuration setting).

Note, DO NOT REMOVE OLD MESSAGES for the old statuses yet, as they are still being used by the live gadget

Acceptance criteria

  • Change the statuses config to match the above table
  • The "Under review" status should be the default for new wishes and focus areas.
  • When voting is not allowed for a given status, the Support button should be hidden and different text shown accordingly.
    • For the "Under review" status: This wish is currently under review. Once accepted, you will be able to support it.
    • All other non-voting statuses (declined/done): This wish currently has N supporters. Supporting this wish is currently disabled.
  • The "Completed" status should appear in green, as per the designs.

Derived Requirements

  1. Update the $wgCommunityRequestsStatuses configuration to reflect the new statuses and descriptions listed in the table.
  2. The default status for newly created wishes and focus areas must be "Under review".
  3. The Support button behavior must depend on the status:
    • If voting is allowed → Support button visible.
    • If voting is not allowed → Support button hidden, replaced with explanatory text.
  4. For "Under review" status, show message:
    • *“This wish is currently under review. Once accepted, you will be able to support it.”*
  5. For other non-voting statuses (*Declined, Done*), show message:
    • *“This wish currently has N supporters. Supporting this wish is currently disabled.”*
  6. The "Done" status (Completed) must appear in green styling according to design guidelines.
  7. Old statuses and their messages must remain available temporarily for compatibility with the live gadget.
Test Steps

Test Case: Status update and voting rules

  1. Navigate to the Community Wishlist and create a new wish.
    • ✅❓❌⬜ AC1: Verify that the default status is "Under review".
    • ✅❓❌⬜ AC2: Verify that the Support button is not shown.
    • ✅❓❌⬜ AC3: Verify that the following message is displayed: *“This wish is currently under review. Once accepted, you will be able to support it.”*
  1. Change the wish status to Unsupported.
    • ✅❓❌⬜ AC4: Verify that the Support button is shown (voting allowed).
  1. Change the wish status to Community opportunity, Long-term opportunity, Near-term opportunity, or Prioritized.
    • ✅❓❌⬜ AC5: Verify that the Support button is shown (voting allowed).
  1. Change the wish status to Declined.
    • ✅❓❌⬜ AC6: Verify that the Support button is not shown.
    • ✅❓❌⬜ AC7: Verify that the message is displayed: *“This wish currently has N supporters. Supporting this wish is currently disabled.”*
  1. Change the wish status to In progress.
    • ✅❓❌⬜ AC8: Verify that the Support button is shown (voting allowed).
  1. Change the wish status to Done.
    • ✅❓❌⬜ AC9: Verify that the Support button is not shown.
    • ✅❓❌⬜ AC10: Verify that the message is displayed: *“This wish currently has N supporters. Supporting this wish is currently disabled.”*
    • ✅❓❌⬜ AC11: Verify that the status chip for Done appears in green.

QA Results - Meta Beta

Event Timeline

MusikAnimal changed the point value for this task from 2 to 3.
MusikAnimal updated the task description. (Show Details)
dmaza changed the task status from Open to In Progress.Jul 25 2025, 2:48 PM
dmaza claimed this task.

Change #1175629 had a related patch set uploaded (by Dmaza; author: Dmaza):

[mediawiki/extensions/CommunityRequests@master] [WIP]

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

@JWheeler-WMF

When voting is not allowed for a given status, the Support button should be hidden and different text shown accordingly.

Currently it says "This wish currently has N supporters. Voting for this wish is currently closed."

What would be the "different text shown accordingly" part? I'm unclear about what needs to change here other than hiding the button accordingly


  • The "Completed" status should appear in green, as per the designs.

Can we do the last bullet point in a follow up patch?

yes we can do the last bullet in a follow up task.

I'd just hide the button and say "supporting this wish is currently disabled."

I would say for "Under review" we don't want to indicate the number of supporters (since it will always be zero). So we could just hide the "Voting" section altogether in that case. Otherwise, the current messaging is fine, I think.

The button was removed entirely from PHP in r1175175. So whether or not to show it is only a matter of:

  • Adding the .ext-communityrequests-voting-btn container – already respects the status' voting option, and
  • Loading the ext.communityrequests.voting module – currently this only looks at CommunityRequestsWishVotingEnabled / CommunityRequestsFocusAreaVotingEnabled and not also the status, but incidentally this is fine since the init script looks for the container element which won't be present if voting is disabled.

Why would wishes under review not be eligible for voting? It is a good
signal for us to see how the community prioritizes wishes.

So, for Done, and Declined we show the Voting section with the message This wish currently has XX supporters. Supporting this wish is currently disabled.
And for "Under review" we hide the section entirely.

Why would wishes under review not be eligible for voting? It is a good
signal for us to see how the community prioritizes wishes.

@JWheeler-WMF Joy has a point

Given Joy's POV, I am OK with enabling the support button for wishes under review . The wish should be marked for translation only after it's gone beyond the review state.

The text looks good to me.

Change #1175629 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Update Entity Statuses

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

Why would wishes under review not be eligible for voting? It is a good
signal for us to see how the community prioritizes wishes.

Given Joy's POV, I am OK with enabling the support button for wishes under review . The wish should be marked for translation only after it's gone beyond the review state.

The problem is wishes evolve, but not so much after they've been reviewed and marked for translation. The process of reviewing a wish is supposed to result in a clearly defined problem that can be feasibly taken on by WMF or other stakeholders, then it is marked for translation, which sort of "locks" it in because further edits have to be reviewed. Until that point, you may have ambiguous, solution-focused wishes that could lead to misguided votes. If we go this route, I think we need to at least prioritize T399500: Add remove support button to wish and focus area pages.

There's also the potential for support-bombing of something we don't want, i.e. "Dismantle the wishlist". We'd be removing that barrier if we allow voting as soon as a wish is submitted, if that's of any concern. I personally was more concerned about the "misguided vote" problem, though. I.e. see this discussion for example, which is what led us to implement the auto-incrementing titles like W123 for similar reasons – wishes and their meanings can evolve.

If we need to use voting as a means to gauge public interest before we even review wishes, then I think that indicates a problem with our ability to review them in a timely fashion.

At any rate, it will only involve a configuration change should we change our minds.

Change #1176582 had a related patch set uploaded (by Dmaza; author: Dmaza):

[mediawiki/extensions/CommunityRequests@master] Display entity status 'Done' in green

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

Change #1176582 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Display entity status 'Done' in green

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

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

[mediawiki/extensions/CommunityRequests@master] AbstractTemplateRenderer: add a 'style' prop to configuration

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

+1 to @MusikAnimal above. We should not allow voting on wishes until they have been reviewed

If we decide to block voting before a wish is accepted by us, the message should say

"This wish is currently under review. Once accepted, you will be able to support it". The text mentioned in the acceptance criteria with 0 vote count sounds off in this context.

@Cparle @JSengupta-WMF Can you update the task desc to reflect what we want when you make a decision?

Change #1177512 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] AbstractTemplateRenderer: add a 'style' prop to configuration

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

Update: we're disallowing voting when wishes are under review as we need to take a first pass if the wish is relevant.

Change #1181826 had a related patch set uploaded (by Dmaza; author: Dmaza):

[mediawiki/extensions/CommunityRequests@master] Disallow voting when status is under-review

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

Change #1181826 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Disallow voting when status is under-review

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

@dmaza Please Review AC3. Texts from the task description do not match the result.

**Test Result - Meta Beta*

Status: ✅ PASS/ ❌ FAIL
Environment: Meta Beta
OS: macOS Sequoia 15.6.1
Browser: Chrome 139
Device: MBA
Emulated Device: NA

Test Artifact(s):
https://meta.wikimedia.beta.wmcloud.org/wiki/Special:WishlistIntake

Test Steps

Test Case: Status update and voting rules

  1. Navigate to the Community Wishlist and create a new wish.
    • AC1: Verify that the default status is "Under review".

2025-09-02_14-07-26.png (1,288×930 px, 154 KB)

  • AC2: Verify that the Support button is not shown.

2025-09-02_14-06-42.png (1,260×994 px, 184 KB)

  • AC3: Verify that the following message is displayed: *“This wish is currently under review. Once accepted, you will be able to support it.”*

See AC2

  1. Change the wish status to Unsupported.
    • AC4: Verify that the Support button is shown (voting allowed).

2025-09-02_14-39-29.png (1,112×974 px, 184 KB)

  1. Change the wish status to Community opportunity, Long-term opportunity, Near-term opportunity, or Prioritized.
    • AC5: Verify that the Support button is shown (voting allowed).
Community opportunity- VectorLong-term opportunity- TimelessNear-term opportunity- MinervaPrioritized- Monobook
2025-09-02_15-01-08.png (1,112×993 px, 192 KB)
2025-09-02_15-02-10.png (896×982 px, 142 KB)
2025-09-02_15-03-42.png (1,050×992 px, 144 KB)
2025-09-02_15-05-15.png (1,169×786 px, 188 KB)
  1. Change the wish status to Declined.
    • AC6: Verify that the Support button is not shown.

2025-09-02_15-05-59.png (1,150×889 px, 168 KB)

  • AC7: Verify that the message is displayed: *“This wish currently has N supporters. Supporting this wish is currently disabled.”*

See AC6

  1. Change the wish status to In progress.
    • AC8: Verify that the Support button is shown (voting allowed).

2025-09-02_15-09-55.png (1,156×905 px, 173 KB)

  1. Change the wish status to Done.
    • AC9: Verify that the Support button is not shown.

2025-09-02_15-10-31.png (1,148×898 px, 168 KB)

  • AC10: Verify that the message is displayed: *“This wish currently has N supporters. Supporting this wish is currently disabled.”*

See AC9

  • AC11: Verify that the status chip for Done appears in green.

See AC9

GMikesell-WMF updated the task description. (Show Details)
GMikesell-WMF updated the task description. (Show Details)
❌ AC3: Verify that the following message is displayed: *“This wish is currently under review. Once accepted, you will be able to support it.”*

This requirement was added after the patch was merged so it was not included. I'll create a follow up patch. Thanks

Change #1187009 had a related patch set uploaded (by Dmaza; author: Dmaza):

[mediawiki/extensions/CommunityRequests@master] Display different message when entity status is under-review (default)

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

Change #1187009 merged by jenkins-bot:

[mediawiki/extensions/CommunityRequests@master] Display different message when entity status is under-review (default)

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

❌ AC3: Verify that the following message is displayed: *“This wish is currently under review. Once accepted, you will be able to support it.”*

This requirement was added after the patch was merged so it was not included. I'll create a follow up patch. Thanks

@dmaza Ok I now see the update as seen in the screenshot below. I will mark this as Resolved now. Thanks for all your work!

✅ AC3: Verify that the following message is displayed: *“This wish is currently under review. Once accepted, you will be able to support it.”*

2025-09-23_11-57-19.png (931×981 px, 143 KB)

GMikesell-WMF updated the task description. (Show Details)