As a product manager, I want to know whether a new feature that uses messages A, B, C... has been translated to languages X, Y, Z before deploying there.
This could done with a new special page with two inputs:
- List of languages
- List of message keys
For convenience, it would be helpful to be able to give prefix(es) of message keys. We have existing pattern processor, that would allow prefixes and more.
It would be helpful if the results page could be easily be bookmarked and shared as a link. It would also be helpful to know whether all the translations have been exported and/or deployed, but this might require quite bit of more effort, so perhaps leave it out of scope for now and consider as follow-up.
Operational considerations:
- Since we only cache messages for message groups, not arbitrary list of messages, we should impose limits on the number of languages and message keys.
See also T59514: Special:MessageGroupStats for a list of languages – difference is whether to use a list of message keys vs. a message group.
Proposed design: Expand the existing Message Group stats page
The current Message group statistics page may be covering most of the needs to check the translation status. The main limitations seem to be in the selection of the specific messages to get the stats for. Currently is is only possible to select message groups, so it is not possible to select a specific sub-set of messages for a given feature.
This proposal is about making the selection more flexible, so that it is possible to:
- Select message groups from a list, as in the current page.
- Select message groups by searching them. Which would make it more convenient given the current long list.
- Select individual messages by searching a fragment of their ID. Making it easy to find a message even if the whole ID structure is unknown.
- Define a prefix to select all messages related to a feature.
- Discover all the above possibilities without knowing them upfront.
To support this the idea is to replace the current drop-down with an input field with as-you-type search results panel surfacing the relevant options. This is illustrated below:
 |  |  |
Future iterations can consider supporting multiple selection, either as part of the same input (e.g., communicate that adding a comma can select multiple messages), or with a different input supporting multiple values.