| Note |
|---|
SERVER ONLY! |
| Table of Contents |
|---|
Enabling the logs
Links Hierarchy writes traces in JIRA logs. However, this feature is disabled by default and you have to explicitly authorize the plugin for that:
...
Keep in mind that the configuration above is automatically reset if JIRA is re-started so you have to grant the plugin to write in the JIRA logs again.
...
Export to Excel 404 error
| Tip |
|---|
Resolved from version 5.3.3 Since version 5.3.3 it is not necessary to set Jira local URL. If you experience any problem when exporting to Excel after updating to version 5.3.3, please clear the browser cache. |
...
Configure the DNS used by the Jira host to resole the proxy name
Add the proxy name and address to the /etc/hosts file
Time outs in the logs / Incomplete hierarchies / blank JQLs / CPU & Performance issues (ADVANCED)
Sometimes Links Hierarchy might require a lot of time to read all the data, this might require consuming Jira resources (CPU, Threads, RAM, etc) for a long while that might cause performance issues.
...
In other words, the process of reading data works for 250 milliseconds, then goes to sleep for 100 milliseconds in a loop. After 10 seconds the process is aborted causing incomplete hierarchies for every issue hierarchy. In addition for JQL, there is one-minute timeout to complete the work.
...
In the case of the jql's, if TIMEOUT_JQL is exceeded, the execution of the jql will be aborted and will return an empty set of data
The SLEEP parameters can be modified to allow the process to read data faster and the TIMEOUT for more time.
The number of free resources (threads, CPU, and RAM) on Jira are limited and shared with the rest of the apps. Of course, there is not one simple pattern for all the organizations: the default parameters are quite conservative and they work fine in most organizations, however, some hierarchies may require more time. A more aggressive approach like
SLEEP_INTERVAL: 1000
SLEEP_DURATION: 25
TIMEOUT: 20000
might allow reading all the data. Depending on the number of links, users' concurrency and peaks of work, the plugin can be optimized to load more data.
If some hierarchies are not being fully loaded (time out errors in the Jia logs when the plugin traces are enabled), the Jira administrators can tune the plugin to allow reading all the data while Jira is also being monitored.
Those parameters can also be modified in the Jira database directly:
...