Hello,
We're using the Jira Cloud app for Slack.
We are a multinational company, with people using Jira in several languages.
So, when an issue is posted in Slack, the information displayed are in a various number of languages, depending of the one defined in the Atlassian account of people.
I would like to know if there is a way to configure the language used to display the issue information in Slack, so that it takes English by default, and not the language of the Atlassian account of the user who posts the issue.
Thank you.
Hi @Emilie ,
As I can see, the only one supported language is English:
Better contact the Atlassian support team and ask them to raise a suggestion/feature request.
Hope it helps!
Thanks for the feedback.
The field names are indeed in English, but their value is in the user language.
For example, we'll have:
- Status: "To Do" // Type: "Story" - for an English user
- Status: "A faire" // Type: "Histoire" - for an French one
I think I'll end up contacting Atlassian support :).
Have a good day!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not yet - I've just sent the question Friday afternoon.
I'll post their answer here when I get it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing sure for now: Atlassian support is going to check the configuration in my instance, so that they can set the same on theirs, and try and reproduce the issue. They'll open a Feature request or a Bug depending on the results they get.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian support confirms they can reproduce the issue and is collaborating with their developers to see what can be done.
I'll tell you as soon as they get back to me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here the lastest message from Atlassian: "Devs are working on the issue and have found out the root cause of the problem that you are facing. They are trying to develop a fix and will update us once they have the solution loaded into the main code base."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Latest update: "The new fix was deployed in our staging and then to production. There are some reviews pending and I am following up with the developers to see if I get a confirmation that the feature is released to the Prod sites."
It should be good soon! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.