Steps to replicate the issue:
- Preview {{#CommunityRequests:data|id=W123|field=status}}
What happens?:
"Long-term opportunity"
What should have happened instead?:
"long-term-opportunity"
Other information:
This makes the feature useless for coding with {{#ifeq:}}, {{#switch:}}, etc., since the result depends on page language.
Derived Requirement
Ensure that the parser function {{#CommunityRequests:data}} returns the internal status name (e.g., 'long-term-opportunity') rather than the translated human-readable status (e.g., 'Long-term opportunity'), so that the output is stable and suitable for use in parser logic such as {{#ifeq:}} and {{#switch:}} across all interface languages.
Test Steps
Test Case 1: Ensure {{#CommunityRequests:data}} Returns Internal Status Value
- Open any wiki page on the beta environment for editing.
- Insert the following wikitext: {{#CommunityRequests:data|id=W29|field=status}}
- Preview the page.
- Observe the returned value.
- Confirm the language of the page does not change the output.
- Confirm that the returned value is the internal key (e.g., 'long-term-opportunity') not the translated label.
- ✅❓❌⬜ AC1: The parser function returns the internal status name, not the translated version.
- ✅❓❌⬜ AC2: The returned value remains stable and identical across different interface languages.
QA Results - Meta Beta
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T409615#11445088 |
| 2 | ✅ | T409615#11445088 |