If an Error occurs in our Jira-Plugins, you can send us Log files from the System. This helps us to solve the Error faster. This How To describes the steps to create the required log files. Therefore you need the Jira System Administrators Permission.

Step 1 - Enable the Logging

  • Open the Jira Administration and go to the Logging & Profiling settings.
  • Scroll down to the Section "Default Loggers" and click "configure".

  • A dialog opens where you must enter the package name. The package names for our plugins are listed in the next section. Be sure to set the Logging Level to "DEBUG".

Package names 

Agile Hive

net.seibertmedia.agilehive

ICS - Issue Calendar Sync

net.seibertmedia.Jira.plugins.issuecalendarsync

Knowledge Base Custom Field 

net.seibertmedia.Jira.plugins.kbcustomfield

Project Role Inspector

net.seibertmedia.Jira.plugins.projectroleinspector

InstaPrinta

net.seibertmedia.Jira.plugin

Collective Issue View for ServiceDesk

net.seibertmedia.Jira.plugins.civ

Publish Issuesnet.seibertmedia.Jira.plugins.pi
AutoPagenet.seibertmedia.jira.plugins.autopage
Custom Epic Panel

net.seibertmedia.jira.plugins.agilehive.epp

Step 2 - Reproduce the Error

Redo the Steps with the Plugin which occur to your described behavior. 

Step 3 - Location of Logfiles

The Error should now recorded in the  "atlassian-jira.log". The logfile is stored in the file system of the server. To get the complete path:

Open the Jira Administration go to System/System info.

    • Scroll down to the section "File Paths". Here you find the Location of atlassian-jira.log.  

Now you can send us the log files.

Don't forget to disable the DEBUG logging for the Plugin. To disable the Logging follow the description in step 1, but instead to configure a logger, search the created logger (package name) in the table and choose the option "WARN".

This content was last updated on 12/06/2021.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete.

Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with content@seibert.group if you are in doubt, have a question, suggestion, or want changes from us.