Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

internationalization doesn't work in my velocity template

IMENE FIRAS
September 5, 2021

Hi, Community,

in my Jira plugin, I have created a servlet module that renders a Velocity file.

the problem is that internationalization doesn't work only in this file which is rendered by servlet, however, it works the rest of velocity files created by other modules.

when I have for example:

<h1>$i18n.getText("key. Title")</h1>

it renders ' $i18n.getText("key.title") ' in the interface.

I added my velocity file in atlassian.plugin.xml like that:

<web-resource name="gedSearcher" i18n-name-key="ged-searcher.name" key="ged-searcher">
<description key="ged-searcher.description">The gedSearcher Plugin</description>
<resource name="ged searcher" type="velocity" location="templates/GEDSearcher.vm"/>
</web-resource>

but it still doesn't work, could anyone help me please to solve this problem!

2 answers

0 votes
Joe Pitt
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 Champions.
December 29, 2015

I agree with Phill, use project roles whenever possible.

0 votes
Phill Fox
Community Champion
December 29, 2015

Hi Craig,

At some point someone will have to manage your list to cater for new arrivals, changes of role and departures. So you could be considering how best to handle this.  You presumably have a user management process in place?

A few approaches will work.

  1. Define the list of users in the filter query - means the owner of the filter is responsible for updating the list and would be required to edit for each filter on a change.
  2. Use the groups but as you have already seen this requires a global administrator to manage the list.
  3. Use project roles which allows the project lead or anyone with delegated authority the permission to manage the members of a role.

Personally I always recommend 3 as it gives the responsibility for the project to the project lead. Although there are some instances where I revert to 2 where it is a more global membership that needs setting.

Hope this helps.

Phill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events