error when changing default language of jira service desk

[Henk Smets]

I want to change the default language of JSD (cloud). 

I can select another language, after submitting I get the error message "can't be saved".

From the page "Language support" I choose "Change default language", after selecting the 1 possible new language and pressing "Change" I get this error message:"Your changes couldn't be saved. Try again."

Every text has an translation, my personal language setting gives the same result.

[Timo Fitzner]

Hey Angelica,

i have a similar Problem. It´s not Possible to change the Language. 

I checked the answers from above, but it didn´t work for me. 

Can you help me?

[Henk Smets]

Hi Timo,

In our case there was a corrupt service request.

I needed help from atlassian to remove this service request.

regards,

Henk

[Angélica Luz]

Hi @Timo Fitzner,

The most common case is when the issue type is not associated with the project.

Did you follow the steps below:

First, you need to go to Project settings > Request types and check the issue types that are associated with the request types.

You can take note of all issue types or you can click on each one to check if it shows any error.

Then, on Project settings, click on Issue types > Action > Edit issue types > Drag and drop the necessary issue types to "Issue types for current scheme" > Save.

In Henk's case, we were able to identify that there were duplicated issue types, so it was necessary to contact support in order to delete it from the database (we don't have access to it from a question in community). 

If you have few Request types on the project, you can open one by one to check if it shows any error as I mentioned before and if that's the case, then just associate the issue type to the project or delete the request type.

Regards,
Angélica

[Angélica Luz]

Hi Henk,

Thank you for reaching out to Atlassian Community!
Just for us to better understand and help you with this issue, can you please open the developer tools on your browser and check if it shows any other error message when you try to change the default language?
Have you tested using incognito mode or other browsers?
Are you the only user facing this issue when trying to change the language on the personal settings?

Regards,
Angélica

[Henk Smets]

Hi Angélica,

Changing the personal settings is no problem. But I'm trying to change the default language of the JSD project in de project settings. I added in my original support question that it makes no difference which personal language setting I had set.

regards,

Henk

[Angélica Luz]

Thank you for the details.
I understood that you were having issues in both personal settings and language support.
Can you check the details I sent previously about opening developer tools while changing the default language and use incognito mode?

[Henk Smets]

Hi Angélica,

Error-message from console dev tools chrome in NORMAL mode:

language:1 Access to fetch at 'https://mgas.prod.public.atl-paas.net/v1/event' from origin 'https://vlaamseoverheid.atlassian.net' has been blocked by CORS policy: Request header field x-atlassian-mau-ignore is not allowed by Access-Control-Allow-Headers in preflight response.batch.js?adg3Enabled…erational=true:4455 POST https://mgas.prod.public.atl-paas.net/v1/event net::ERR_FAILEDlanguage:1 Uncaught (in promise) TypeError: Failed to fetch

Error-messages from console dev tools chrome in INCOGNITO mode:

Error-message:

https://vlaamseoverheid.atlassian.net/rest/servicedesk/lingo-integration/1/manage-language/13887batch.js?adg3Enabled=true&agile_global_admin_condition=true&devsummary=true&globalSidebarEnabled=true&jag=true&jaguser=true&jiraSpaIframeApi=true&locale=en-UK&sd_operational=true:4455 POST https://vlaamseoverheid.atlassian.net/rest/servicedesk/lingo-integration/1/manage-language/13887 500

 Code:

/* module-key = 'com.atlassian.analytics.analytics-client:js-events', location = 'js/node_modules/@atlassian/cloud-analytics-js/user-activity-xhr-header.js' */
define("atlassian/analytics/user-activity-xhr-header",["atlassian/analytics/page-visibility"],function(g){var e="x-atlassian-mau-ignore";var f=XMLHttpRequest.prototype.send;var c=window.fetch;var h=XMLHttpRequest.prototype.open;var a=false;var l=Object.create(null);var k=new RegExp("^(?:[a-z]+:)?//","i");var d=function(m){var n=document.createElement("a");n.href=m;return n.hostname};function i(p,n){var o={};for(var m in p){if(n.indexOf(m)>=0){continue}if(!Object.prototype.hasOwnProperty.call(p,m)){continue}o[m]=p[m]}return o}function b(o,q){var p=typeof o==="undefined"?window:o;var n=typeof q==="undefined"?setTimeout:q;var m=false;return function(s){if(m){return}m=true;try{n(function(){throw s},0);if(p.AJS&&Array.isArray(p.AJS.EventQueue)){var r;if(s instanceof Error){r=s.stack||s.message||"Unknown"}else{r=String(s)}p.AJS.EventQueue.push({name:"fetch.override.error",properties:{error:r}})}}catch(s){}}}function j(m,o,n){return function(p,u){var q=u;try{if(o.isHidden()){var t=(u||{}).headers;var r=typeof t!=="undefined"?new Headers(t):new Headers();r.set(e,true);q=i(u,["headers"]);q.headers=r}}catch(s){n(s);return m.call(this,p,u)}return m.call(this,p,q)}}return{install:function(){if(!a&&g.supported){XMLHttpRequest.prototype.open=function(n,m){this._url=m;return h.apply(this,arguments)};XMLHttpRequest.prototype.send=function(){var m=k.test(this._url)?d(this._url) in l:true;if(g.isHidden()&&m){this.setRequestHeader(e,g.isHidden())}f.apply(this,arguments)};if(c){window.fetch=j(c,g,b(window))}a=true}},uninstall:function(){if(a){XMLHttpRequest.prototype.send=f;if(c){window.fetch=c}}a=false},addHost:function(m){l[m]=true},createReportErrorOnce:b,createOverrideFetch:j,ACTIVITY_IGNORE_HEADER:e}});require("atlassian/analytics/user-activity-xhr-header").install();;
;

[Angélica Luz]

Hi Henk,

Thank you for the screenshots.
I was able to find this error on our logs:

Uncaught exception thrown by REST service: java.lang.RuntimeException with stacktrace: java.lang.RuntimeException at com.atlassian.servicedesk.internal.multilanguages.ClassicLingoToDomainObjectUpdaterImpl.copyLingoDefaultTranslationToDomainObjectTables(ClassicLingoToDomainObjectUpdaterImpl.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56) at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor$1.run(ServiceTCCLInterceptor.java:61) at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:130) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokePrivileged(ServiceTCCLInterceptor.java:58) at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133) at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213) at com.sun.proxy.$Proxy5099.copyLingoDefaultTranslationToDomainObjectTables(Unknown Source) at com.atlassian.servicedesk.plugins.lingo.integration.internal.managelanguage.ClassicLingoProjectDefaultUpdater.lambda$updateDomainObjectTablesBecauseOfProjectDefaultChange$0(ClassicLingoProjectDefaultUpdater.java:40) at io.atlassian.fugue.Option$Some.forEach(Option.java:468) at com.atlassian.servicedesk.plugins.lingo.integration.internal.managelanguage.ClassicLingoProjectDefaultUpdater.updateDomainObjectTablesBecauseOfProjectDefaultChange(ClassicLingoProjectDefaultUpdater.java:39) at

Usually, this issue is related to request types associated with issue types that are not available in the project.
First, you need to go to Project settings > Request types and check the issue types that are associated with the request types.
You can take note of all issue types or you can click on each one to check if it shows any error.

Then, on Project settings, click on Issue types > Action > Edit issue types > Drag and drop the necessary issue types to "Issue types for current scheme" > Save.

After that, try to change the language again.

[Henk Smets]

Hi Angelica,

Thank you for the reply. I found one request type which probably causes the error. I can't delete it because it asks for the related issuetype to be added to the issue type scheme of the JSD project. The issue type is probably changed, so I can't add it back.

I added all existing issuetypes to the issuetype scheme of the project and still I couldn't remove the request type. Is there a way to delete the request type directly in the database?

[Angélica Luz]

Thank you for the information.

Can you send a screenshot of the error when you try to delete the request type?

Is it happening when you click on the X next to the request type or you are following other steps to remove the request type?

Please, confirm if the issue type still exists on Jira settings > Issues > Issue types. If not, please create a new one using the same name, add to the issue type scheme in the project and try to remove the request type.

[Henk Smets]

Hi,

When I click on the "x" besides the request type, I'm getting an spinning wheel forever. see screenshot1

When clicking "edit fields" of the request type I get an error message. see screenshot2

Translated to english: "You cannot edit the request type because the issue type on which it was based has been deleted. Place the related issue type back into the issue type scheme of this project to restore the request type."

The issue type of this request type is named "incident" with a blue icon. see screenshot1. So the issue type has the same name, only the icon is different, I cannot remember altering other things. To test this I added all issue types to the issue type scheme. I could not delete the request type when I added all the issue types to the issue types scheme.

[Angélica Luz]

Thank you for the screenshots, Henk.

That duplicated issue type may be causing this, but I'm not sure how to replicate since Jira shouldn't allow the creation of another issue type using the same name.

Do you know how this issue type was created? Was there any CSV import in this project?

If this issue type is not being used on another project, can you go to the Jira settings > Issues > Issue types and rename this issue type? Then try to remove again.

[Henk Smets]

The icon of the issue type incident was changed. I don't recall exactly how anymore. It is possible that I duplicated the issue type and later deleted it. I don't think I changed the generic issue type, because the issue type is used by other projects.

I do not see it on the issue type page (global jira settings). See screenshots. I don't find a duplicate filtering by the name "incident" or the icon.

There were no CSV imports in this project. As far as I Know.

Is there a possibility to delete the request type in the database? Or are there too much dependencies? Can the exact linked issuetype be found in the database?

[Angélica Luz]

Thank you for all the information, screenshots and tests.

It's really weird that it's showing this duplicated issue type and as this instance is on Cloud, you can't remove it from the database, but we can check if this issue type exists in the database and remove it and also remove the affected request type.

For that, I created a ticket with our support, since we need to deal with sensitive information.

You will receive a notification and soon someone will contact you. 

[Henk Smets]

Thank you.