Thanks, Vera, for raising the idea. Could you elaborate what a query sheet is specifically in your case? You mean like an Excel?

Just a note, that we have plans on our roadmap to build out native query management functionality.

That's great news! Right now we use an Excel sheet, but I don't think that the optimal way to manage queries. My idea would be to add a tab to the Project view like so: 

And it would list all the queries the translators have posted. It would pull the data from the online editor, so you would be able to see what segment, what file and what context the query was posted in.

For the translator view, perhaps they could post their queries from within the Online Editor in a separate tab, same as a segment-specific comment. And then when the replies come in, they'd be able to see that in the Query tab as well, as well as filter for segments with queries.

Other nice to haves would be:

• Make it part of the QA check - if a query is still open, files can't be delivered. The translator has to tick a box next to the query that says "Query reply implemented" to confirm they've seen the reply and implemented it.
• Add an option to mark a query as language-specific OR applicable to all languages. So that the PM can decide, is this something that all languages need to look at and implement (example: source errors), or is it just for the language that asked the query
• Add this as a datapoint to the Report functionality - so that we can see how many queries get asked for what types of projects, and how long it takes to get replies.
• Give the PM the option to assign queries to be answered by other users, such as software developers for software L10n

That's great news! Right now we use an Excel sheet, but I don't think that the optimal way to manage queries. My idea would be to add a tab to the Project view like so: 

And it would list all the queries the translators have posted. It would pull the data from the online editor, so you would be able to see what segment, what file and what context the query was posted in.

For the translator view, perhaps they could post their queries from within the Online Editor in a separate tab, same as a segment-specific comment. And then when the replies come in, they'd be able to see that in the Query tab as well, as well as filter for segments with queries.

Other nice to haves would be:

• Make it part of the QA check - if a query is still open, files can't be delivered. The translator has to tick a box next to the query that says "Query reply implemented" to confirm they've seen the reply and implemented it.
• Add an option to mark a query as language-specific OR applicable to all languages. So that the PM can decide, is this something that all languages need to look at and implement (example: source errors), or is it just for the language that asked the query
• Add this as a datapoint to the Report functionality - so that we can see how many queries get asked for what types of projects, and how long it takes to get replies.
• Give the PM the option to assign queries to be answered by other users, such as software developers for software L10n

Thanks, Vera. You should become a Product Manager ;), because it goes along the exact lines we are thinking of.

I can't give any timelines right now, and certainly not in 2023, but it's something we are looking at

Thank you! I enjoy this kind of topics so I'm happy to give feedback :)

Hi Luis,

Any updates on when something like this may be added? This would be super helpful for our linguists.

Thanks,

Russell