**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**
1. Open any wiki page on the beta environment for editing.
2. Insert the following wikitext: `{{#CommunityRequests:data|id=W123|field=status}}`
3. Preview the page.
4. Observe the returned value.
5. Confirm the language of the page does not change the output.
6. Confirm that the returned value is the internal key (e.g., 'long-term-opportunity') not the translated label.
7. Confirm that the value can be used reliably inside logic constructs such as `{{#ifeq:}}` and `{{#switch:}}`.
8. ✅❓❌⬜ **AC1:** The parser function returns the internal status name, not the translated version.
9. ✅❓❌⬜ **AC2:** The returned value remains stable and identical across different interface languages.