Description
Most times, problems can be resolved by discussion of the symptoms and/or having recreation steps that can be reproduced. In some cases, this may not be sufficient and may require some additional data collection. This can be done relatively easily with support available in JIRA, Confluence, and Bamboo for adding temporary logging levels without requiring a server restart. See the links below for more details. This involves turning on DEBUG logging for specific packages.
For most plugins provided by Bob Swift Software, the easiest (most general package) thing to use is org.swift. This should be fine for 99% of the cases. More specific packages may be needed to reduce the amount of logging if more than one plugin has been installed and there is heavy use.
Newer add-ons may use the com.appfire prefix - for example CODE and BSQLT.
Steps
- Follow the Atlassian product specific instructions to enable org.swift package level DEBUG.
- Perform the steps that cause the problem.
- Go to the server and find the application server log file.
- Attach the relevant sections out of the application server log (or the entire log) to the JIRA issue you have created.
...