Raising a request with Atlassian Support

If you encounter any problems when setting up or using Bitbucket Server, please let us know — we're here to help!

If you're on a starter license, we suggest you check out the following resources:

If you're interesting in upgrading to get private technical support, have a read here to get an idea of what needs to be done.

If you've found a bug in Bitbucket Server, or want to request a feature or improvement, raise a ticket in the Bitbucket Server project of our public issue tracker. Try searching for similar issues - voting for an existing issue is quicker, and avoids duplicates.

If you still need assistance, please raise a support request, either from within Bitbucket Server or on the Atlassian Support site, as described in the following sections.

Providing as much information as possible about your Bitbucket Server installation with your initial request will help our Support Engineers to give you a faster and more complete response.

On this page:

Raising a Support Request in Bitbucket Server

To use this method a mail server that supports large zip file attachments must be configured.

To raise a support request in Bitbucket Server:

  1. Log in as a System Administrator.

  2. Go to > Troubleshooting and support tools > Get help.

  3. Click Contact Technical Support or Report a Bug.

  4. Create your support request. You’ll need to include:

    • Contact email – This defaults to the email address of the logged-in user. It’ll be used to find your support account or, if no account is found, to create a new account. We'll send all notifications and updates about your problem to this address.

    • Summary – Enter a short summary of the problem.

    • Description – Include as much information as possible about the problem, such as steps to replicate the problem; messages on the console or in the log; and profiling logs if you’re having a performance issue. See also Information you should provide below.

    • Severity – Choose an option to indicate how many users are affected.

    • Attach support zip – When this is selected, a zip file of your logs and configuration files will be attached to your support request. This can speed up troubleshooting the problem and it should be included if possible. See Create a Support Zip for info on what's included.

  5. Click Send.

After sending your support request you’ll receive an email with the information you entered. You’ll also receive email updates about progress on the problem.

To see the status of your request visit the Atlassian Support System.

Raising a support request yourself at Atlassian Support

To raise a support request at Atlassian Support:

  1. Log in as a System Administrator.

  2. Go to  > Troubleshooting and support tools > Create support zip

  3. If necessary, click Customize zip to choose what is included. For help, see Create a support zip.

  4. Click Create zip.

  5. Click Download zip to save it to the home directory of your Bitbucket Server instance. For example, <Bitbucket home directory>\shared\export\Bitbucket_XXX.zip.

  6. Go to Atlassian Support and create a support request with the downloaded support zip.

When creating your support request, provide as much information as possible. Include steps to replicate the problem; messages on the console or in the log; and profiling logs if you’re having a performance issue. See also Information you should provide below.

Information you should provide

In addition to the logs and configuration information that you can include in the Support Request zip file, the following information can help to give you a faster response:

Environment details

  • Bitbucket Server version
  • Java version (for example OpenJDK 1.7.0 JRE)
  • Git and Perl versions
  • Operating system (for example, Windows 7, macOS 10.6.8)
  • Database type (for example, MySQL) and version
  • Browsers and versions
  • Network topology - is Bitbucket Server running behind a reverse proxy? Is that secured using HTTPS (SSL)? 


  • Java settings, including JVM_MINIMUM_MEMORY, JVM_MAXIMUM_MEMORY


You may need to adjust the logging level, or enable profiling in Bitbucket Server, in order to get more detailed logs. See Bitbucket Server debug logging.

  • Debug logs – Bitbucket Server debug logs can be found in  <Bitbucket home directory>/log.
  • Profiling logs – Bitbucket Server profiling logs can help with analyzing performance issues and can be found in  <Bitbucket home directory>/log.

Performance factors

  • Number of concurrent Git clones
  • Number of users
  • The size of the .git directory
  • CPU spec, number of cores, whether hyperthreading is enabled
  • RAM and cache sizes


  • Other Atlassian applications (and their versions)
  • Which build servers are integrated with Bitbucket Server, if any?
  • Are Application Links configured?
Last modified on Mar 30, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.