| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
This is information about troubleshooting of JSU in generalpage provides general troubleshooting tips for the JSU app. If you have a problem with encounter problems using a particular module, please also check refer to the documentation for that module or refer to 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, analysed analyzed your log files, and tried different configurations, but it still does not work, feel free to submit a support ticket: Support portalyet continue to have issues, get in touch with our Support team.
| Table of Contents | ||
|---|---|---|
|
Some or all functionality not working
...
In rare cases, Jira has difficulties may have difficulty enabling JSU. Usually, this can be solved by uninstalling/re-installing, reset, or reload, etc. things.
We recommend checking the following things:
Manage add-ons: is
the JSU app enabledJSU enabled, and all modules enabled
(except one, which is disabled per default!)?
Check your log files, serious problems usually leave a stacktrace. Do you see a reference to a class
?com.googlecode.jsu.*
determentdetermine which module cannot be loaded)?
Re-install the app
...
Reinstall JSU
Have you tried to remove the JSU app and reinstall it in the Jira administration? (Without restarting Jira)
See also https://confluence.atlassian.com/upm/uninstalling-Atlassian's guidance on uninstalling add-ons-273875709.html .
If re-installation of the app in the reinstalling JSU in Jira administration does not work, try to do it with a restart of Jira, follow this steps:
Uninstall JSU
Stop
...
Jira
Perform a backup of your
...
Jira installation and database
If you could not uninstall JSU before, delete the file
$JIRA_HOME/plugins/installed-plugins/*jira-suite-utilities*.jarDelete the following
...
two directories:
$JIRA_HOME/plugins/.bundled-plugins
...
and
$JIRA_HOME/plugins/.osgi-plugins(they will be recreated)Start
...
Jira
Install JSU
...
| 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 re-installationto reinstall the app, but at the end just install the an older version.
| Warning |
|---|
| Note |
You might lose some functionality and or potentially re-introduce some bugs , that have been fixed in the a newer version. So generally Generally, it is not a good idea to downgrade JSU. Further if you have saved any configuration Configurations saved with a newer version of JSU (in particular in the area of workflows), the configuration saved with a newer version of JSU 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, for example when navigating to JSU General Configuration. Checking . Check the log file there had been messages likefor messages similar to the following:
| Code Block |
|---|
Error creating bean with name 'com.googlecode.jsu.actions.ConfigurationAction': Unsatisfied dependency expressed through constructor argument with index 0 of type |
This issue was because of due to a conflict with some other pluginanother add-on. We had been able to fix resolved this issue in JSU version 2.5.2. We recommend updating to the latest version of JSU.
...
Debug the JSU app
If you want to turn on the 'JSU' debug messages, you may do so as follows:
Temporary (until next JIRA restart):
Log in to Jira as 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 |
|---|
com.googlecode.jsu |
as Package name and select DEBUG as Logging Level
...
Repeat for
| Code Block |
|---|
ch.beecom.jira.jsu |
Permanently
...
Add the following lines into to the file WEB-INF/classes/log4j.properties:
| Code Block |
|---|
log4j.category.com.googlecode.jsu = DEBUG, filelog log4j.additivity.com.googlecode.jsu = false log4j.category.ch.beecom.jira.jsu = DEBUG, filelog log4j.additivity.ch.beecom.jira.jsu = false |
| Warningnote |
|---|
Debug log messages are very detailed. Your log file will grow very quickly, even and the performance of the whole system can be affected. For these reasons, we recommend leaving We recommend enabling the logging only for a very short time on debug log level. |
...