...
This page provides general troubleshooting tips for the JSU app. If you encounter problems using a particular modulefeature, please refer to the documentation or search our knowledge base. We recommend you test your workflows in a test project or separate test instance before committing your rules in production.
If you have read our documentation, analyzed your log files, and tried different configurations, yet continue to have issues, get in touch with contact our Support team.
On this page:
|
|---|
Some or all functionality not working
...
| Info |
|---|
No configurations (for example workflow or customer field related) will be removed when reinstalling, however, it's always a good idea to perform a backup. |
Install an older version of JSU
Follow the steps to reinstall the app, but install an older version.
| Note |
|---|
You might lose some functionality or potentially re-introduce some bugs that have been fixed in a newer version. Generally, it is not a good idea to downgrade JSU. If you have Configurations saved any configuration with a newer version of JSU, the configuration might not be compatible with an older version of JSU. ( We provide only compatibility for updates of JSU). |
Bean dependency problems with messages in the log file
In rare cases, we have had reports that users received a 404 error message in the browser. Check the log file for messages similar to the following:
...
To enable JSU debug messages:
Temporarily (until the next Jira restart)
...
Log in as a Jira administrator and go to System > Troubleshooting and Support > Logging & Profiling.
Locate and select Configure logging level for another package.
Enter:
...
| Code Block |
|---|
ch.beecom.jira.jsu |
Permanently
...
Add the following lines to the file WEB-INF/classes/log4j.properties:
...
| Note |
|---|
Debug log messages are very detailed. Your log file will grow very quickly, and the performance of the whole system can be affected. We recommend enabling the logging only for a very short time on debug log level. |
...