For JIRA, Confluence and Bamboo

The logging level can be increased for troubleshooting. To do this, go to the JIRA/Confluence Logging and Profiling (in the Administration section) (for Bamboo Log settings) configuration and add following new entry:

com.resolution with DEBUG level



After that, the plugin starts detailed logging in the

<JIRA home directory>/log/atlassian-jira.log  

<Confluence home directory>/log/atlassian-confluence.log

<Bamboo home directory>/logs/atlassian-bamboo.log


For Bitbucket

To increase the plugin logging level for the troubleshooting in Bitbucket, please follow the steps below:

  1. Mark the checkbox Enable debug logging in the Bitbucket Logging and Profiling configurations:

  2. You can choose now between adding the plugin debug logging packages at startup or at runtime:

    1. To enable plugin debug logging whenever Bitbucket Server is started, edit the <Bitbucket home directory>/shared/bitbucket.properties file (if this file doesn't exist then you should create it) and add the following line:
      logging.logger.com.resolution=DEBUG

    2. To enable plugin debug logging once Bitbucket Server has been started, edit the <ADMIN_USERNAME> and  <BASE_URL> part with your informations and run the following command in your terminal:

      curl -u <ADMIN_USERNAME> -v -X PUT -d "" -H "Content-Type: application/json" <BASE_URL>/rest/api/latest/logs/logger/com.resolution/debug


After that, the plugin starts detailed logging in the <Bitbucket home directory>/log/atlassian-bitbucket.log.


For Fisheye/Crucible

To increase the plugin logging level for the troubleshooting in Fisheye/Crucible, go to the Server (in the Global Settings section) configuration and Turn Debugging On in Debug Logging section.



After that, the plugin starts detailed logging in the <Fisheye/Crucible instance directory>var/log/atlassian-fisheye-<current date>.log