Is workflow statuses can be translate in request type

[XXY]

reference:  https://support.atlassian.com/jira-service-management-cloud/docs/customize-the-workflow-statuses-for-a-request-type/

[Walter Buggenhout]

Hi @XXY,

The customer facing status on request types is not supported for translation, unfortunately. It is best to use generic enough names there so they support your customer base as much as possible.

Hope this helps! 

[XXY]

Thank you for your response.

Now i know the answer exactly.

[Marc -Devoteam-]

Hi @XXY 

What is you exact question.

The option show is to provide the customer a different name for a workflow status on the customer portal.

You can also set the same name for multiple a statuses, e.g. if you would have multiple statuses that would imply that the issue is worked on, you could then set them all to the name "In Progress".

This will limit the status change notification an the custom would see the issue as In Progress on the portal, but in the backend the issue could have a different status.

This does need to be set per request type.

This is not a translations option.

For Translation, see https://support.atlassian.com/jira-cloud-administration/docs/translate-resolutions-priorities-statuses-and-issue-types/ 

[XXY]

Thank you for your response.

Our workflow status is more than 30.

Sometimes, customers in portal unsure whether current status requires them to take action or just wait for agent, so i think set status alias can help them understand this situation.

Currently, portal support  two langs, so i came here to seeking opinions.

[Marc -Devoteam-]

Hi @XXY 

Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.

This will help other community member trying to solve the same or provide them with a work around

P.S. If the answer is very valuable to you, please share some kudos.