About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips


Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects

BigPicture Cloud Backlog

About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms


Knowledge Base

Tutorials and tips

Trust Center

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Cloud, Server and Data Center users. Visit BigPicture 8 Documentation to learn more about it.

Before installation, go to Atlassian Marketplace and check which Jira versions are compatible with BigGantt

After BigGantt app is upgraded or enabled, the app runs a full scope synchronization process of all existing active (not closed) Programs. As a result, there is an increased probability that all active Programs will be synchronized once a user wants to open a given Program and start working with it.

Jira Server/Cloud

Universal Plugin Manager

We recommend this way - Atlassian's Universal Plugin Manager will always install the latest version of our plugin and - what's more important - the one appropriate for your Jira instance. You have to be logged in on admin account, then go to Jira Administration → Add-ons → Find new Add-ons and search for "BigGantt". Depending on the fact if you've already installed BigGantt in the past or if you are new to the application, you will see "Install" or "Free Trial" button. Press it and you are all set.


Alternatively, you may go to Atlassian Marketplace and download a version which is most suitable for you. Please bear in mind though that it is a always a good practice to keep your application up to date along with updated Jira. Be careful to choose the version for your Jira instance! When sure, click on the desired version to expand its row. Hit "Download" on the right-hand side.

Only thing left is to upload the file to Jira. This can be done in Jira Administration → Add-ons → Manage Add-ons. Select "Upload add-on" on the right-hand side.

Be aware that this installation method is the only method which can be applied in case of installing the app in Jira Data Center.

Installing in Jira Data Center

The Jira Data Center configuration can only be established when the system is able to identify the presence of Jira Data Center environment. In such environment, all data is being replicated into cluster nodes with the use of Hazelcast technology. It is possible to set up a port, which will be listened to by specific cluster nodes. With such a factor, we’d create a situation similar to the one described in Atlassian’s official JIRA DataCenter documentation article under the ehcache.listener.port paragraph ( file parameters).

Regular installation

To set up the port described above, it is required to add a parameter to JVM runtime parameters under which a specific node within a cluster is established (as per instruction provided by Atlassian in the following article: Setting properties and options on startup).

The parameter should be set as follows:


Full integration of BigGantt in Jira Data Center has been implemented with the release of BigGantt 3.4.0 therefore the above configuration may be obsolete in that (and following) version of the application as for the clustering purposes our app will allocate all necessary port value to the one seen below, during the installation in the Jira Data Center: BigGantt - 40104.

Though, it is required for this port to be open on each DC Node in order for our apps to execute and function properly.


In order to perform a clean installation of BigGantt in your environment, please do the following:

  1. Disable the app

  2. In the JIRA database, please delete all of tables which begin with: AO_8AC478_

  3. Execute the following script:

delete s from propertystring s
inner join propertyentry p on =
{{where p.property_key = }}


  • No labels