| 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. |
...
Frequently, Jira is host on some server at then corporation intranet behind a proxy server with a public URL (please see the picture below): User types the public URL in the browser (https://mycompany/jira) which is forwarded by the proxy to the internal server hosting Jira (https://hostname:8080/jira). The plugin uses the public URL (https://mycompany/jira) to access to the Jira host (https://hostname:8080/jira) to export to Excel. This may cause 404 HTTP errors as a lot of times, the DSN used by the Jira host is not aware of the proxy (public) URL,
...
Set Jira local URL (Recommended)
In newer versions it is possible to set the Jira local URL:
...
Configure the Jira host DSN
Unfortunately, in earlier versions of the plugin, it is necessary to help the plugin to reach the proxy by:
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.
...