Cloud vs. Data Center - Key Differences between Platforms

Introduction

With each new release of our Cloud-hosted plugins, we endeavor to reduce disparities in functionality and customization between them and our Data Center-hosted versions. However, due to technical prerequisites and limitations of Jira Cloud, inevitable variances remain.
Our Data Center-hosted BigPicture remains the gold standard, serving as a reference point for its Cloud-hosted equivalent.
In the tables below, you can find such disparities by comparing and contrasting the features and functionalities of Cloud- to Data Center-hosted BigPicture and BigPicture Enterprise modules.

Since BigPicture includes all of BigGantt's functionalities, BigGantt was intentionally missed out in the below comparison.

Clear cache

Most problems with outdated information that cause errors can be resolved by clearing the cache.

Refer to the Plugin cache page for further instructions.

Modules

In this table, you can check the availability of modules in BigPicture Cloud and BigPicture Data Center versions.

Module

BigPicture Cloud

BigPicture Data Center

Module

BigPicture Cloud

BigPicture Data Center

New Gantt

Yes

Yes

Scope

Yes

Yes

Board (SAFe® )

Yes

YES

Objectives (SAFe® )

Yes

YES

Resources

Yes

Yes

Risks

Yes

Yes

Teams

Yes

Yes

Calendar

Yes

Yes

Reports

Yes

Yes

The list of missing functionalities in BigPicture Cloud – issues on BigPicture's side

Module

Key difference

Explanation

Preview

Issue to track

Module

Key difference

Explanation

Preview

Issue to track

Risks, Board

Edit Issue dialog not available on Cloud

Not available at the moment.

Edit option in task view

 

Feature request on BigPicture's end.

Note: inline editng allows you to edit visible card fields.

Alternatively, click on the issue key to open the issue page to make changes.

All

Online presence

Not available at the moment.



Feature request on BigPicture's end:

https://appfire.atlassian.net/browse/BP-4273

All

Enhanced JQL functionality

Jira Cloud doesn't support JQL enhancement.

 

Feature request on BigPicture's end:

https://appfire.atlassian.net/browse/BP-9023

The list of missing functionalities in BigPicture Cloud – issues on Atlassian's side

Module

Key difference

Explanation

Preview

Issue to track

Module

Key difference

Explanation

Preview

Issue to track

Gantt

Create Jira sub-task not available on Cloud

Atlassian Connect Jira JavaScript API does not provide such functionality.

Jira sub task highlighted in a drop-down menu

 

Ticket on Atlassian's end - click here.

Scope

Detail View not available on Cloud

Atlassian API does not provide such functionality.

 

Ticket on Atlassian's end - click here.

BigPicture configuration

"Risk consequence" "Risk probability" and Task Mode fields are locked

Atlassian's REST API allows the plugin to add Select List (single choice) type of fields on installation only when they are locked.

For more information, refer to this article.

 

 



BigPicture configuration

Respect Jira's Screen scheme configuration

The UI element (swiper) is not available. The Jira Cloud hosting security always requires respecting the screen scheme configuration, so the administrator has no possibility to configure the application in this regard.





Confluence

Gadgets

Following differences in the Confluence architecture between Jira Data Center and Jira Cloud:

  • Gadgets from Jira Data Center are automatically available with the same login mechanisms;

  • Gadgets from Jira Cloud were removed on July 7th, 2017 (you can find details in this JIRA Knowledge Base).

-



If you have any further questions or are still in doubt about why certain options or features remain inaccessible, contact our Support Team via our Service Desk.

Custom fields from third-party Jira apps in BigPicture and BigGantt.

Depending on the functionality of a given plugin, custom fields based on third-party Jira apps may have limited or different functionality in the Cloud version of the product. For example, Traffic Lights can be displayed only as a text field.