There are messages for describing the status of focus areas and wishes, for supporting them, etc. The same messages are used for both wishes and focus areas. The problem with this is that some languages need different words for wishes and focus areas. In Hebrew, Italian, and probably in many other languages "wish" and "focus area" need adjectives from different grammatical genders. That's an example of incorrect message re-use.

The messages should be split—one message for wishes and another for focus areas.

The ones I could identify are:

• communityrequests-status-under-review
• communityrequests-status-unsupported
• communityrequests-status-declined
• communityrequests-status-community-opportunity
• communityrequests-status-long-term-opportunity
• communityrequests-status-near-term-opportunity
• communityrequests-status-prioritized
• communityrequests-status-done
• communityrequests-support-dialog-title

It's possible that I missed some, but it's OK to start from these.

Derived Requirement

Ensure that Community Requests uses separate localized message keys for *wishes* and *focus areas* to prevent incorrect grammatical gender or contextual usage in languages where the two terms differ. Each of the following shared messages must be split into two distinct message sets—one for wishes and one for focus areas:

• "communityrequests-status-wish-under-review": "Under review",
• "communityrequests-status-wish-accepted": "Accepted",
• "communityrequests-status-wish-unsupported": "Unsupported",
• "communityrequests-status-wish-declined": "Declined",
• "communityrequests-status-wish-community-opportunity": "Community opportunity",
• "communityrequests-status-wish-long-term-opportunity": "Long-term opportunity",
• "communityrequests-status-wish-near-term-opportunity": "Near-term opportunity",
• "communityrequests-status-wish-prioritized": "Prioritized",
• "communityrequests-status-wish-in-progress": "In progress",
• "communityrequests-status-wish-done": "Done",

• "communityrequests-status-focus-area-under-review": "Under review",
• "communityrequests-status-focus-area-accepted": "Accepted",
• "communityrequests-status-focus-area-unsupported": "Unsupported",
• "communityrequests-status-focus-area-declined": "Declined",
• "communityrequests-status-focus-area-community-opportunity": "Community opportunity",
• "communityrequests-status-focus-area-long-term-opportunity": "Long-term opportunity",
• "communityrequests-status-focus-area-near-term-opportunity": "Near-term opportunity",
• "communityrequests-status-focus-area-prioritized": "Prioritized",
• "communityrequests-status-focus-area-in-progress": "In progress",
• "communityrequests-status-focus-area-done": "Done",

Test Steps

Test Case 1: Verify separate localized messages for wishes

1. Navigate to a Community Requests page displaying a wish (e.g., Special:CommunityRequests/Wishes).
2. Observe the status and support-related messages shown for the wish.
3. ✅❓❌⬜ AC1: Confirm that the messages use the new wish-specific keys and translations (e.g., communityrequests-wish-status-under-review).

Test Case 2: Verify separate localized messages for focus areas

1. Navigate to a Community Requests page displaying a focus area (e.g., Special:CommunityRequests/FocusAreas).
2. Observe the status and support-related messages shown for the focus area.
3. ✅❓❌⬜ AC2: Confirm that the messages use the new focus-area-specific keys and translations (e.g., communityrequests-focusarea-status-under-review).

QA Results - Meta Beta