GTLBAB-15 + workaround to get Argo request URL from TOS
Hey team,
I launched a new request that can be directly accessed here: https://gitlab.spartansoftwareinc.com/#workspace/request/GTLBAB-15
This request adds a new file to the argo_translation.yml file: environmental-social-governance.yml. We have translated this page before on https://gitlab.spartansoftwareinc.com/#workspace/request/CTFL-101 but the file was a json there.
We went over it in person @carla.tocco and I to better understand what information you got.
From the meeting we can conclude that:
- Translated don't receive a direct link to the Argo request and/or the Source MR.
- As the steps on GTLBAB requests aren't assigned to Translated alias, the requests don't appear under their tasks dashboard.
- Providing the links through the API is possible and it will reduce the manual work on Translated project managers
- The manual work consists on pasting the request key on the search bar and also clicking on the Source MR in the translation request.
- There is a possible workaround:
- As the translation key is provided through the API and it's the name of the order (see screenshot), Translated can replace the translation key in the following URL and they'll access the request directly:
https://gitlab.spartansoftwareinc.com/#workspace/request/[+request key]- https://gitlab.spartansoftwareinc.com/#workspace/request/GTLBAB-10
- https://gitlab.spartansoftwareinc.com/#workspace/request/GTLBAB-15
Given that we still need Translated project managers to analyse the order/request and launch it in Matecat, I suggest Translated project managers use the URL workaround proposed above for some time. We will put in our roadmap the Argo-TOS integration optimization so that we can pass the Argo request URL and/or the Source MR. @katia2 @carla.tocco is this something that you think you can try? I understand that having the URLs automatically passed over the API would be more efficient but we also need to plan on our side Spartan's time. Let us know, please!