Hey @Cristina Gatt,
For attachments themselves, JSM Cloud doesn’t have a native setting that takes a customer-uploaded file, translates the document, and adds the translated copy back to the same request. JSM language support covers the portal, help center, email, and form experience around the request, so this requirement needs an attachment-localization integration or a small custom integration.
If the file itself must be translated, the closest off-the-shelf option I found is Smartcat’s Jira integration. It specifically says it can fetch Jira ticket attachments, translate them, and sync the translated files back to Jira. I am in no way, shape or form affiliated with Smartcat, but it looks like that might address your use case. It appears they offer a free trial if you want to try it out with your real file types and security requirements before committing.
I have built something similar to this in the past. If you want to go down this route, then you could use Forge or an external middleware to listen for a new attachment, download the original file, send it to your document translation service, upload the translated output back to JSM, and add a short comment such as “English translation attached for review.” Forge supports Jira attachment events, and the JSM REST API supports the customer-request attachment flow.
For the upload-back step, use the JSM request attachment API when the translated file should be visible in the portal.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.