Change Details

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 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} – difference is whether to use a list of message keys vs. a message group.

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 messgae 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} – difference is whether to use a list of message keys vs. a message group.

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 messgae 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} – difference is whether to use a list of message keys vs. a message group.