How to set Request Language for requests created with the REST api

Ellie Bellemans

As far as I understand, Request Language is a (locked) custom field. I can see all custom fields for a request type with  

GET /servicedeskapi/servicedesk/2/requesttype/{requestTypeId}/field

but Request Language isn't one of them. 

I understand that since the request is submitted on behalf of a user (in this case the user to whom the api key belongs) and as such, the Request Language should be a field on the request form so it shows in the list of custom fields (correct?) but when I try to add it to the form I get the following warning 

Is there a way to provide a preset value? And is this the correct approach?

Another option would probably be to change the default language of the user to whom the api key belongs (haven't tried it yet so not sure if this is correct) but since we forward requests from our app through our backend, it would be nice if we can inherit the user's app language when creating the ticket.

So what is the advised way to set the request language using the REST api?

 

Many thanks

Angélica Luz

Hello @Ellie Bellemans,

Thanks for reaching out to Atlassian Community!

The Request language field is automatically filled based on the browser’s language or the one the customer selects in their profile on the customer portal. 

 

That’s why when adding the field to the request form, it will be hidden and it’s not possible to set a default value because there is already a default one, which is the default language of the project (Project settings > Language support).

With this said, it will also not be possible to set the value using API when creating tickets on behalf of the customer.

There was a feature request suggesting this ability, but it was closed as “Won’t fix” since there was only one vote since it was created:

• Service Desk API should support Request Language when creating requests

I added an internal comment with the link to this question on the ticket above and since it’s not possible to vote, feel free to add a comment and watch to receive updates.

Currently, there is no workaround for that since the field is also not supported on Automation.

Kind regards,
Angélica