Backup and restore BigPicture using CSV file
BigPicture visualizes data from connected tools, such as Jira.
Jira lets you export data in CVS format. You can export data regarding selected issues (for example, a single project). The backup file can include all existing Jira fields, including custom fields.
Data can be selectively restored from a file. You can specify the field for which you want to make changes. Other fields can be left in their present state.
This process can't be used to restore the WBS structure. It is strictly used to change the values of Jira fields.
Export
To prepare for export, go to Issue Search. Use JQL filters to display the issues you want to create a backup for.
For example, the "Allocation Details" box has only one Jira project in its scope.
This makes creating a backup file for this box easy. However, a more complex set of JQL filters could be used to include multiple Jira projects or just a limited number of tasks from a project or projects.
Next, export the data into the CSV file.
Prepare the app for import
Before the import, you may want to change the period mode in which Gantt tasks operate to manual in some cases. This will prevent any automatic calculations from being performed in BigPicture.
Without this change, the restore process of timeline-related data (start date, end date) has a chance of failure if the existing automatic rules don't allow for making a given change.
To perform this change, select the Data → Task mode → Manual on the Gantt, which will be restored.
Import data into Jira
Importing an external project lets you selectively overwrite data instead of creating new issues and projects.
To initiate the import, select the Import External Project option from the Jira Project dropdown. For official documentation, visit Atlassian documentation for Running the CSV file import wizard.
Do not use the Issue dropdown, which has a position called Import issues from CSV. This option will not allow you to overwrite the data and will force you to create new items.
For official Atlassian documentation on importing Jira Project from external sources while updating existing Jira issues, please visit this documentation article.
Especially if Jira issues come from different Jira projects, use data included in the CVS file to overwrite existing issues within those projects.
Field mapping
Always include the following fields:
issue key → This will ensure that Jira issues will get updated instead of creating new ones
Summary → Summary
Project name → Project name
Project key → Project key
Project type → Project type
Additionally, select which fields you want to be overwritten. In the example below "Start Date" and "End Date" fields are selected.
Need support? Create a request with our support team.
Copyright © 2005 - 2026 Appfire | All rights reserved.
