| Table of Contents | ||||
|---|---|---|---|---|
|
...
I'm applying E2F app on a DC environment with 4 nodes. On two of the nodes, when I go to create a new "Feature", it is still showing as "Epic" on the issue type field?
Go to the issue type schemes that had the "Feature" issue type and re-arrange the order of issues on the nodes that were causing the problem. Here's a link to the Atlassian Jira ticket for reference: https://jira.atlassian.com/browse/JRASERVER-64106?error=login_required&error_description=Login+required&state=79673a5c-66d6-4d66-935f-ecc697972ddb
...
For example, let's say you have a reference to an "Epic Link" in you code like this:
string epicLink = #{Epic Link};
If you create an alias in the alias file, it would look like this:
#{Epic Link}=#{Feature Link}
In this example, any time "Epic Link" is referenced in a script, it will update "Feature Link" because of the alias.
Why is Issue Type displayed incorrectly on the Create Issue and Edit Issue screens?
Once you have translated Issue Type 'Epic' according to the steps described here, it may require to update your Issue type Schemes which are used. To do this, go to Administration → Issue Type Schemes, select necessary Scheme and click Edit (though no changes needed), and then click Save.
Why some users don't see the translation?
One of the reasons is that the user profile language is different from the selected locale on the configurations page. Please note, that translation dialog contains the locale. The translations are implemented only for the locale that is selected on a screen. On the certain pages (for example - the Special Translations page, First page of the configuration page wizard) you are able to select the Translate all option to implement the translation to any language. But on some native Jira pages (for example - Custom Fields, Issue Type) you need to manually input new value for each language so that the translations are displayed correctly.