Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this page

Support Options for this Product

Find answers from the community.

Ask a question to the community.

Log a request with our support team.

Request support

If you have a usage question

Ask a question on this site using Confluence Questions. You will need to be logged in. An alternative is to add a question to the Atlassian Community site. 

We recommend that you create a support request if you have a complex usage question or you need to provide attachments and detailed information.

If you need an improvement added to an app

Please create an improvement request.

If you have a bug to report

Please go to the app's project in Jira and search for an existing issue or create an issue.

If you need support

Please create a support request.  An alternative is emailing

Sign in required to participate in the community

This site is viewable by anonymous users. To participate in the community, you are required to have or create an Atlassian account and sign in. Participants can ask and answers questions, watch pages, and create and watch issues. Visit Atlassian Community for additional information and links.

To provide quicker and more accurate responses to issues or emails, please include as much information as possible on the initial request including:

  1. Version of the plugin or app - put in the Affects Version/s field in the issue
  2. Version of the Atlassian product - put in Environment field in the issue 
  3. Steps to recreate, including wiki markup or command or configuration information

For CLI tools, also see How to get CLI help, support, and fixes.

Our support policy

In order to be entitled to support, the following conditions must be met:

Support policy for Server

  • License must have a non-expired maintenance window.
  • App version must be used with compatible host server version as indicated in the Marketplace listing.
  • The latest app version compatible with the host server version is supported. You will be asked to upgrade to the latest app level for problem determination and fixes in most cases.
  • General rule is to support at least host server versions released within the past year. Limited support may be available for earlier versions up to their end of life (EOL) following Atlassian Support End of Life Policy
  • A version, in our terminology, means a release indicated by x.y (like 4.1). Minor/maintenance versions (like 4.1.1) are not counted.

Support policy for Cloud

  • Cloud instances are automatically updated unless our app requires authorization for additional permissions in which case the update is delayed until an administrator approves.

Our support SLA

We strive to provide prompt, effective support to our clients. This page describes our Service Level Agreement (SLA) targets.

Response times

Expect a response to support requests within 1 business day (24 hours). Tickle the issue if response seems too long (smile).

Business hours

Monday to Friday (except for major US holidays), 7am - 7pm ET,  4am - 4pm PT, 12:00 - 24:00 CET.

More limited ability to respond between during US holiday periods. 


The following sources are monitored for requests in priority order. In all cases better problem information helps speed the response and resolution.

  1. Jira issues (preferred) entered directly through our public Jira project associated to the product or via our Support portal (private).
  2. Questions posted on this site or the Atlassian community.
  3. Email to

Fixes and improvements

There is no specific response time for bug and improvement requests, but they are reviewed regularly for consideration to be included in a future release. If you need a response urgently, change the issue type to a support request. Fixes and improvements are made in the next released version of the software based on need and capability. In many cases, an Early Access Program (EAP) release is available containing fixes and improvements to provide more timely response to requests and as an opportunity for customer feedback. Normally, EAP releases are called SNAPSHOTs and pass regression tests, but some changes may be incomplete. Use with caution. 

Priority process

Incoming triage and serious bugs take precedence over other requests. Requests are prioritized based on criteria including but not limited to:

  1. Importance to customer.
  2. Applicability to other customers including votes. Feedback and discussion is important!
  3. Customer is current on maintenance via SEN (Support entitlement number - purchase or evaluation).
  4. Availability of acceptable workarounds.
  5. Grouping with other related work. Backlog issues are reviewed for a planned app release and backlog issues with current activity take precedence.
  6. Scope and risk of change.
  7. Availability of customer to verify a SNAPSHOT solves the problem or request.

Advanced troubleshooting information

Most times, problems can be resolved by discussion of the symptoms and/or having recreation steps that can be reproduced. In some cases, this may not be sufficient and may require some additional data collection. This can be done relatively easily with support available in Jira, Confluence, and Bamboo for adding temporary logging levels without requiring a server restart. See the links below for more details. This involves turning on DEBUG logging for specific packages.

For most plugins provided by Bob Swift Software, the easiest (most general package) thing to use is org.swift. This should be fine for 99% of the cases. More specific packages may be needed to reduce the amount of logging, if more than one plugin has been installed and there is heavy use. 

Newer apps can use the com.appfire prefix - for example Code Pro for Confluence and SQL for Bamboo.

Add DEBUG logging at runtime

  1. Go to Administration > Logging and Profiling.
  2. Find the Add new entry area near the top of the page.
  3. Add the following entry for the Class/Package Names: org.swift.
  4. Select DEBUG for the New Level value and click Add entry.
  5. Log statements are displayed in the standard Jira/Confluence log file.
  6. Go to the server and find the application server log file or create a Support Zip using the Atlassian Tools. 
  7. Attach the relevant sections from the application server log, the entire log file, or ZIP to the Jira issue you have created.
  • Logging occurs immediately, but only lasts until Confluence is restarted.
  • Ensure to go back and remove the entry that was added after you have completed triaging your issue.

No direct access to server log?


This documentation in PDF format

Some people may need a copy of an app's documentation in PDF format. Individual pages can be exported using the Tools > Export to PDF option. However, it may be more convenient to get a PDF for the entire space.


  1. Log into the site. (Only logged in users have access to export documentation).
  2. Go to one of the app pages.
  3. From the Confluence menu, choose Browse > Space Operations.
  4. Select PDF Export.

Still need help?

Help - more general help.

  • No labels