This section does not apply to Jira Cloud users, due to the nature of Jira Cloud hosting.
Technical info and Troubleshooting
|Show cache stats|
Show the number of entries in different caches.
This reports the cache statistics information and is required in case of occurring performance issues.
|Show case providers info||Show all the cache providers.|
Clear the apps cache which will result in full synchronization of all the Programs.
Most of the problems with outdated information which can cause errors can be resolved by clearing the cache.
|Clear permissions cache||Clear the apps permissions cache in case the change in permissions is not recognised by the app.|
|Download all locks data||Generate locks report to identify performance issues.|
|Download all cluster lock data||Generate locks report to identify performance issues for Data Center clusters.|
|Release all clusters locks|
Release all locks on all Data Center clusters.
In JIRA Data Centre some operations require the a lock to be placed across all nodes for operations that should only be operated on one node at a time, for example taking a backup of the index.
While releasing the locks might resolve the performance issues on your instance this information is required to identify the root cause of the problem hence do not release the locks before contacting Support Team.
|Release current node cluster locks||Release current node's cluster lock.|
|Show Integrity checker||Integrity check is the process of comparing the current state of stored data and/or programs to a previously recorded state in order to detect any changes.|
|Fix integrity error||Fix the identified integrity errors.|
|Lock logging||Enable / disable the lock logging.|
This section allows you to perform basic troubleshooting actions or (whenever required) extract information which can be later send to the Support Team.
If you've encountered any issues with the app and the problem persists after updating to the latest version, please contact our Support Team via our ServiceDesk (or by sending an e-mail to: email@example.com) providing as many information describing the error as possible.
Please remember, that the more detail we have on the issue, there's a higher chance that we will be able to help you resolving it in a first reply. Therefore, we are always more than happy, when receiving screenshots pointing to the problem, possibly with highlighted field where the defect occurs.
Along with the above we would need you to send us information on the version of Jira which you are currently using and (if by any means you were unable to make an update to the latest release) version of our application as well as the Fine-grained Log.
There are three logging levels which specify the amount of information which will be stored in our application's logs. :
Any information logged here may be crucial when investigating app's errors, therefore when reproducing an error always set it to 'Fine-grained' level.
|Support data||Send logs to our Support Team directly using the app or download the logs or via our ServiceDesk or by sending an e-mail to: firstname.lastname@example.org|
|Logs button on app screens||Enable / disable the send and download logs button on error notifications.|
|Feedback button on app screens|
Enable / disable the feedback button which found in the right-bottom corner of the screen.
Set the maximum number of tasks that a single Program can hold to limit BP's performance impact on Jira instance. The default value is 100 000 tasks.