It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to retranslate "None" in other language? Edited

The translation of the option "None" in Russian is not completely correct. For example, NONE - it means "no answer" in English, but in the Russian interface it translates like "No". At the same time in answers we can use the option "No" also. To sum up it looks like that: "No, Yes, No, Not necessary'. We need the field "None" as a default field in our Russian checklists, but with other translation. Could you help to resolve the problem? 

3 answers

0 votes


There is a site called that you can use to help translate your instance and help the rest of the Community.  You can find instructions on using the site here.




I still have the problem. I tried to change the translation of "None" on the site, but it was unsuccessfully. I suppose the key of the word isn't right. I also tried to use an instruction on a page for finding the right key,but for Jira it doesn't work. Please, give me some instruction for resolving the problem?Безымянный.png

Please follow the instruction

Use key "common.words.none" to translate it as you want.

2017-11-01 14_00_05-Translations@Atlassian.png

Domenico, thank you for the answer.
I've done what you recomended, I've even translated every possible "None", but the Jira, wich I use, in Cloud and, I can suppose, it has to be updated automatically and I should wait for it. Right?
I still have the problem, though I translated it yesterday. Tell me please, if I do something wrong or tell me how long should I wait for updating.

The process and the result is below:


Olya, it's all very simple.
1. You need to install the plugin:
2. Create a script:


AJS.$('#customfield_00001 option[value = \'-1\']').detach();

Where the field ID is, it's your field's id. (You can see it in the browser inspector)




3. Context for script

You configure the display only for certain or all project contexts.



Except that

1.  Injecting javascript like that is a bad thing to do

2.  It doesn't work on Cloud

1. It often happens that the customer wants a strange one. In current (cosmetic) conditions, it is much better than nothing.

2. Well, thank God.

Just pointing out bad practice, and that a good admin will remove that sort of thing as soon as it's noticed.  And it is one thing Cloud gets right, stopping horrid broken bothces.

I completely agree. But still jsincluder the best replacement  for announcement banner, Which was used and will be used by young admins.

Let better these s..t scripts are loaded only on the right pages, not on each.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Apr 09, 2019 in Portfolio for Jira

Portfolio for Jira 3.0 is here!

The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...

1,270 views 12 24
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you