nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to rename "Issues" to something like "Tickets"

unknown

This would need to apply to the main menu, create issues, filters, reports, etc.

We store more information than issues in Jira (such as user stories, requests, new features) and the term Issues is causing some confusion.

I was thinking maybe in a localisation file somewhere?

Accepted answers

Dieter

This has already been answered at https://answers.atlassian.com/questions/12097/make-changes-in-language_xx_xx-jar-file But please be aware that you have to redo the changes each time you upgrade - really tedious. Try whatever you can to avoid such a change

All comments

Dieter

Kim Sullivan

Redoing the changes every time is much easier if you version the language files. What I've done is this:

get the preferred language file from https://translations.atlassian.com/ (even the english files are there)
sort the properties (for me it was a side effect of using http://sourceforge.net/projects/eclipse-rbe/ but makes automatically merging changes easier)
version the sorted property files (I'm using Git) on the master branch
create a branch for your customizations
create a JAR of your customized property files and upload it to your installation

Now each time I upgrade (or just want to update the translations), I just get the updated version from atlassian translations, sort it again and commit a new version on the main branch and merge it to your "custom branch". There may be some conflicts, but these can be easily resolved.

When you don't have to actually do the translation but can use the files directly from the Jira installation (or the translation supplied by Atlassian is OK), you could probably simplify the whole process (get rid of the sorting and using a property file editor). The crucial thing is to version the original files and to apply your changes in a separate branch so you can merge automatically.

jjaroczynski

Hi Evan,

That's extremely simple right now.

We have just released InProduct translation plugin for JIRA.

It allows to translate JIRA right from its page so you can see all messages and provided translations live in a second. Just install the plugin in JIRA, select "Translate Page" from the user profile menu in JIRA and start translations.

Translations are permanent as long as IPT plugin is enabled (even after JIRA upgrade).

The plugin is available in marketplace: https://marketplace.atlassian.com/plugins/com.atlassian.translations.jira.inproduct
You can install it from the UPM. It works with JIRA 5.1+.

Cheers,
Jacek

jjaroczynski

BTW. If you like the InProduct translation for JIRA and would like to have the same for Confluence then please vote and comment following issue: https://jira.atlassian.com/browse/TRANS-579

Piero Zucchelli

I think it's a great solution

Sharif M

This is a great solution for chaging words/terms that the user can see. Can this also be used to change word/terms to exported files, etc. For example, I have change all instances of 'Issues' to 'Items'... but when exporting to Excel, the new field names are exported correctly. However, I still see "Displaying 5 issues at 08/July/14..." Similar with gadgets. The tool doesn't recognize text within the gadgets.