Translating transition buttons

francis
Atlassian Partner
October 7, 2012

The page https://confluence.atlassian.com/display/JIRA/Workflow+Properties contains an explaination how to change the button label of a transition (using jira.i18n.submit).
From googling around I found some references indicating that the i18n key should be stored in a property file in the jar under JiraWebActionSupport_en_US.properties (for instance for English name)

I'm wondering if there is a different approach which is simpler and more maintainable ? This is for JIRA 5.0.7

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Marcus Silveira
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 7, 2012

Hi Francis,

You can download the language pack specific for the language to be translated at the Atlassian Marketplace or directly on JIRA using the Plugins screen.

If you'd like to change any of the translations made on the language pack, you can download it at marketplace, edit the .jar file and upload to JIRA the edited .jar on the plugins screen.

I believe you could use this belgium language pack that I found on the marketplace.

Hope this helps,

Marcus Silveira

francis
Atlassian Partner
October 7, 2012

Hi Marcus,

Thanks for the hint

We are using English UK as default language, but I couldn't find that one, I guess that the one in the bundled plugins will do ?

Francis

PS. I'm wondering what the Belgian language is - we have 3 official languages in Belgium - French, German and Dutch - will have a look later on.

Marcus Silveira
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 7, 2012

Hey Francis,

The English UK language pack is already bundled on JIRA, so you can find the .jar file at your $JIRA_HOME/plugins/.bundled-plugins.

Regarding the Belgium language pack, I noticed that too. I believe that is only for the dutch language, considering th plugin description. Don't really know why a separate pack for Belgium since there is already a Dutch Language Pack. Maybe there are some differences specific for Belgium?

You can also find Language packs for French and German if you'd like.

Best regards,

Marcus Silveira

francis
Atlassian Partner
October 7, 2012

Sorry to bother you with this but if you upload the plugin from the bundled plugins (without modifications), you get

Could not find a handler capable of installing the plugin at jira-languages-5.0.6-EN_UK.jar. Check that the file is a valid plugin.

Using UPM 2.7.4

Marcus Silveira
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 7, 2012

No problem Francis,

Please try the following to update that file.

  1. Go to '$JIRA_INSTALL\atlassian-jira\WEB-INF\classes'
  2. Make a backup of 'atlassian-bundled-plugins.zip'
  3. Edit the Language pack .jar file inside the original zip
  4. Shutdown you JIRA instance
  5. Remove the contenct of folder .bundled-plugins from $JIRA_HOME\plugins
  6. Restart your instance

This will recreate your bundled plugins based on the contents of the zip file you updated.

You will not have to upload any plugin on JIRA UI. The changes should be already in effect once you access JIRA.

Best regards,

Marcus

francis
Atlassian Partner
October 8, 2012

Hi Marcus,

Finally got it right - I wanted to have an approach to make it maintainable, avoiding to mess around with the atlassian-bundled-plugins.

  1. Download US language pack
  2. Add the button label translations into JiraWebActionSupport_en_US.properties (com/atlassian/web/action)
  3. Install the modified language pack onto the instance using the UPM.
  4. Switch default language to English (US)

Francis

0 votes
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 7, 2012

I don't think so. The key should be available to the workflows and hence should be maintained in the i18N files.

TAGS
AUG Leaders

Atlassian Community Events