Email Support

If you need help with the Git Integration for Jira app, please e-mail us: support@bigbrassband.com.

Please include the "Support Zip" that Jira produces for diagnosing issues.

Also include information about:

  • How long have you been experiencing this problem?

  • If there were any changes to the environment that would be notable?

You can produce the "Support Zip" by following the steps in this article or by accessing http://[JiraServerNameHere]/plugins/servlet/troubleshooting/view/.

Note
Jira Cloud does not have the Support Zip feature.

 

Right click here to open this video in a new browser tab for more viewing options.

Export Jira Support Zip settings to get the best support.

If the support zip is larger than 15 MB (too large for our support system to receive by email) - contact us: support@bigbrassband.com and we will provide a secure location to upload the support zip.

Memory warnings before GC

new! version 4.0

This type of information can be obtained from the logs.

The memory warnings are added to the logs before GC tasks. This provides admins a window for monitoring memory issues. The following data is logged if the threshold is met:

  • amount of free memory in the Java Virtual Machine in bytes;

  • summary size of index files in bytes (for cloned repositories).

Administrators can view these logs and do maintenance routines if needed. You may send the logs to our support email for further analysis.

Log settings
In order to see the log messages, you need to be sure that the logger severity for 'com.bigbrassband.jira.git.jiraservices.jobs' (Jira settings ➜ System) is set up on the INFO or lower (please check it on http://<server>/jira/secure/admin/ViewLogging.jspaJira settings ➜ Logging and profiling).

The Git Integration for Jira app will automatically use the WARN logger severity if the memory size tolerance has been reached. If administrators doesn't want to see such logs in all GC runs, apply the WARN severity level.