This page contains a list of the tools that can be used to efficiently troubleshoot issues with sumUp configurations.
Analyze the atlassian-jira-log file
Analyzing the log files can be a manner of detecting unnoticed errors.
Navigate to the System → Logging and profiling page of your Jira administration.
Use the "gg" shortcut to search for "logging". You need to be a Jira administrator.
Click on Configure logging level for another package in the Default loggers section of the page.
Add the following packages and logging levels:
| Package name | Logging level |
|---|---|
com.atlassian.cps.sumUp | DEBUG |
Note that any changes you make here are not persisted across server restarts.
After successfully investigating your problem we highly suggest decreasing the logging level to ERROR or WARN to avoid the log file being flooded with JWT messages.
Optionally mark your log files with an additional message or temporarily activate Log Rollover while troubleshooting or replicating the problem on the same Logging and profiling page.
If you don't have server access or don't want to manually access the log file on the file system, try our free app LastLog for Jira to view & search through all log files directly within your Jira administration.
Search the log file for sumUp related entries and try to mitigate the problem.
If you could not locate the problem or need help understanding the results, try asking the the community. Our staff is also active in the community.
If you still need help, feel free to raise a support request in our official support portal.
Our support staff might ask you for the content of your log file. If this is the case, you can tremendously speed up the process if you mark the troubleshooting section as describe above and only sent an extract of the relevant information.
Change the logging levels of the sumUp packages back to ERROR or WARN.
If you still have questions, feel free to refer to our support team.
