| Table of Contents | ||||
|---|---|---|---|---|
|
...
Note that such JQL filters will still be displayed with the "Epic" in their JQL field. If you edit such filter, then the word "Epic" will be replaced by issue type ID or custom field ID, see explanation of this here.
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
We have loads of complex scripts in the workflows, listeners that call for certain validation checks for the issue type Epic. Does replacing the word to Feature affect all these existing scripts ? Do we need to modify these scripts to use the custom field ID instead of the issue name for functioning after enabling E2F app ?
E2F app does indeed change the name of targeted custom fields. If your script references these custom fields by name, you must change these references in your script. You can also refer to the custom field by id. This has the advantage that the id will not change even when the name does. The Groovy language itself also may have a feature which supports aliases. Basically the idea would be to create a file that creates references to the custom field name that can be updated in a single file. The alias is like a virtual link in Unix programming (the metaphor is still valid if you think of it as a url link). If you equate the name as it exists in your script with the custom field as it exists on your system (name or id), you will not have to make changes to all your scripts.
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.