f24fc1998546 We couldn't wait for Atlassian to move so we ended up building our own feedback widget around the embedded API. This is not documented anywhere but we just looked at the widget and figured out what API calls it sends out and how it is handled.

For example searching articles in the service desk:

https://jsd-widget.atlassian.com/api/embeddable/{data-key}/search?query={query}&limit=5

For example submitting a ticket on the service desk:

https://jsd-widget.atlassian.com/api/embeddable/{data-key}/request?requestTypeId={requestTypeId}

body: {
  fields: [
     {id: 'summary', value: '{summary}'}
     {id: 'description', value: '{description}'}
     {id: 'email', value: '{email}'}
  ]
}

Now you can build your own with as much customisation as you want

This is somewhat of a dealbreaker for us - would be nice to be able to localize the support widget as we are localizing the rest of our SaaS app. It doesn't seem to be an obvious way to mimic the same functionality ourselves either using the API?

quote: "We will post another update in a few months time"

A few months?? It is not 42 months since the update from April 2021...

Not easy to understand time estimates from Atlassian.

It is a shame to wait three years for translation of some buttons and fields and pay all this time using an incomplete version .

It's understandable that JSD wasn't supporting multiple languages when it was first introduced as an ITSM solution for internal use only. But at least with the addition of a customer service template you cannot longer ignore the fact that customers do expect support in their language. There's no "maybe" or "We'll add that later". A product placed as a customer facing platform and not supporting the customer's language is simply not a solution - it's just unusable.

So, what's the status with

We’re excited to let you know that we’re evaluating this feature for our roadmap. We will post another update in a few months time.

that is now three years old?

You guys really need to sort this out. The widget is practically useless for me now. I think if you would let me translate the labels myself, that would be fine for now... or just add them to the language file? Can't be that hard no?

I made simple example how to do this with custom coding utilizing MutationObserver functionality in modern browsers. You will have to adjust the snippet to your needs but can be done easily

https://github.com/lehmat/jsm-widget-translations-example

It's been 2 years since the last update?? Having support for multiple languages is an important feature to have. Just like @Florian mentioned "the Office National de la Langue Française could audit and fine the companies for not having full translations in French" so this is huge for anyone in Canada using this widget.
This needs to be a higher priority. 200+ votes should be enough to tell you that people are looking for this update

Having the ability to translate the widget would be incredibly helpful. In countries like mine (Chile), I had to create a manual to complete the widget since it is only available in English.

Such an important feature should be already implemented. Please add this possibility because not all our customers can read in English and is very unprofessional to have two languages mixed