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


 BigPicture 7.10 and earlier

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects

 BigPicture release notes

BigPicture Cloud Backlog


About BigGantt

BigGantt installation and updates

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

 BigGantt release notes

 Release notes
 Jira Cloud

 Jira Server


 BigPicture Enterprise
 Jira Cloud

 Jira Server

 Jira Cloud

 Jira Server

 Jira Cloud

 Jira Server

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.

Below sections exhaust the question Should I update my app? after being notified about the closure of a bug or feature. 

 Short about their workflow

Bugs and features have unique workflows varying from the one used for support requests. The end of their lifecycle is presented on the snapshot below. 

Usually, a task (this might be a bug, or a feature) transitions to Waiting for release status once all the internal work is completed, and when the change itself is ready to be released. Such a task awaits other changes that are planned to be merged with the same app version. Normally this takes a couple of days maximum. 

Then, a task gets moved to Closed status. This, however, doesn't mean it's been released for your app version.

To be sure if you should take any action, check if app and hosting in the Fix Version/s field match with your application. See more under Fix Version/s & Affects Version/s meaning short section.

 Fix Version/s & Affects Version/s meaning

Bugs and features look similar in our Jira. Here's an example of how a bug looks like. 

The fields you should pay attention to are listed below. 

For bugs - Fix Version/s and Affects Version/s, and both have the following form: prod/app/hosting/yyyy/mm/dd/x.x.x where:

  • prod - means a prod version that was publicly shared in the Atlassian Marketplace,  
  • app - indicates which app is related,  
  • hosting - specifies whether it is a 1Cloud- or Server-hosted app, 
  • yyyy/mm/dd - is the exact date a given version was released, 
  • x.x.x - is an app version number. 

1For this environment, the form is slightly different: prod/app/jiracloud/yyyy/mm/dd/hh_mm where the only difference is the last part (hh_mm) which indicates the exact time a given version was pushed out to our customers' Jira Cloud sites.  

For features - Fix Version/s only. 

  • No labels