Configure Log Level of WorklogPRO-Timesheets for Jira

Owned by Deniz Oğuz
Last updated: Feb 07, 2019

If you are contacting us for support we may request a log file from you to understand what happened. Most logging, except exceptions, are disabled in a production system by default, to produce logs we need to enable debug level logging for WorklogPRO. Please use this steps to enable debug level logging for WorklogPRO.

  1. After logging into Jira pres 'G' key two times consecutively (like double clicking with a mouse).
  2. This will "Browse Dialog" of Jira to be popup-up on the top center of Jira UI.
    Jira Logging Browse Dialog
  3. Write "Logging" into the text view
  4. Select "Logging and Profiling" option, this will display "Logging and Profiling" page of Jira.
  5. Scroll down a little on "Logging and Profiling" page and click on the link, "Configure logging level for another package."
  6. Fill the options in this dialog as shown below
    Jira setting log level of an add-on
  7. Click on "Add" button to save new log level.
  8. The page will refresh and you should able to see new log level of WorklogPRO in the list of loggers as shown below. It should be set to "Debug" as highlighted in the below screenshot.
    Log Level of packages in Jira
  9. After that you can continue to use Jira to reproduce the error condition. Be sure to perform request activities so that necessary logs are created that will help us to understand what happened.
  10. All logs are saved in ATLASSIAN_JIRA_HOME/log/atlassian-jira.log file. Size of this file may be large, but you can compress it before sending to us. 
  11. Open this file and search for "com.deniz.jira.worklog" you should see logging statements from our add-on. You can filter out all unrelated logging statements from this file if you want.
  12. After sending the file, you should re-open "Logging and Profiling" page and turn logging off for "com.deniz.jira.worklog" package or set it to "WARN" (recommended). Excessive logging may affect performance.