Support for Atlassian Server Products (and apps like BigPicture) is ending in February 2024.

Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email

Import from a file


To unlock import features, install the BigTemplate App from the Atlassian Marketplace.

You can easily import your task templates from tools like MS Project, MS Excel, CSV, or OpenDocument files.

Box Admins and Jira Admins can import tasks from a file. When the “Permissions for everyone” option is enabled, every logged-in user can import tasks from a file.

To import tasks from a file, click the "+" button and select the following option (keep in mind that import functionality is also available in the Scope module):

Upload a file

Next, select the file you want to import. The maximum file upload size is 300MB.

The following file types are supported:

  • .mpp,

  • .mpx,

  • .xls,

  • .xlsx,

  • .ods,

  • .csv 

Import data from MS Project

Once you import a file from MS Project, all columns with data will be automatically detected. You can check a list of supported fields in the table below
The "Issue Type" for the imported tasks will be set to the default "Issue Type" in Jira. It is also possible to enable the "Convert parent tasks to Jira Epics" option.

Import data from MS Excel / OpenOffice

When importing MS Excel or OpenOffice files, you need to define the columns corresponding to the imported data. To simplify this step, the application tries to recognize the column names and completes the fields accordingly.

The task fields marked with an asterisk are mandatory. Additionally, you can set the relationships between tasks ("Parent Row" and "Link" columns).

The "Issue Types" from the imported file will be replaced with their corresponding "Issue Types" in Jira. Sub-tasks and basic tasks are not supported for the "Issue Types". 

If there are no "Issue Types" defined in the imported file or they are not recognized, the default "Issue Type" will be assigned to the imported tasks in Jira. 

You can also enable the "Convert parent tasks to Jira Epics" option.

Import tasks without dates

The import mechanism allows to support tasks with a single date, or undated tasks in the file. These tasks will be imported with one date, or without dates.

Supported fields 

The table below presents the supported fields for particular files. 

Supported field

Files - .xls, .xlsx, .csv, .ods (column name)

Files - .mpp, .mpx (column name)

Supported field

Files - .xls, .xlsx, .csv, .ods (column name)

Files - .mpp, .mpx (column name)



("Task Name")

Start Date

("Start Date")


End Date

("End Date")


Issue type

("Issue Type")




("Resource Name")

Original Estimate

("Original Estimate")





Baseline Start Date


("Baseline Start")

Baseline End Date


("Baseline Finish")



("% Complete")

Select a Jira project

To carry out the import successfully, you need to define a Jira project where the imported issues should be created. Tasks are visualized in the App and they have to exist somewhere in Jira itself. 

You can:

  • Use one of your current projects. New issues will be added to the existing ones.

  • You can also set up a new, empty Jira project in advance. It is possible to create a new Jira project using the "Create with shared configuration" option. This will result in copying the Jira project setup (permission, notification, issue security, workflow, issue type, issue type screen, and field configuration). For more information, refer to the screenshots below.

Now, choose your Jira project from the drop-down menu.

Convert parent tasks

If you import tasks from an xlsx/csv/odt file, you can define the issue type for these tasks. To do so, you need to add the "Issue Type" column and complete it for each task (e.g., Bug, Story, Epic). The issue type is identified by its name, and uppercase letters are ignored. 
If there is no "Issue Type" column or it is empty, the imported tasks will get the default "Issue Type" as defined for a particular project in Jira.

You can also enable the "Convert parent tasks to Jira Epics" option. As a result, the parent tasks will be converted to Jira Epics regardless of the issue type they had in the imported file (the values from the file for the parent tasks will be replaced with the "Epic" type in Jira). 

Field mapping

When importing from CSV or Excel tables, you need to match the columns from the selected file to the corresponding task fields, as presented below. 

You have to complete the required task fields:

  • Summary

  • Start date

  • End date

Optionally, you can provide additional task fields:

  • Parent row

  • Link

  • Issue type

  • Original estimate

  • Assignee

XLSX data format

If the .xlsx file has been created by exporting BigPicture data, the file can be easily used for import.

Otherwise, ensure that data is formatted in the following way: 

Start date, End date - can be read in the following formats:

  • yyyy-MM-dd (e.g. 2021-12-31)

  • dd-MM-yyyy (e.g. 31-12-2021)

  • MMM/dd/yyyy (e.g. Dec/31/2021).


Example of a "yyyy-MM-dd" date format:


Parent Row - the Excel row in which the parent of the task is

Link - a cell with dependencies / links, for example: 16FS-1 or 21SS+1, where:
16, 21 - pointer to Excel's row with the linked task;
FS, SS - link type:

  • FS - finish to start;

  • SS - start to start;

  • FF - finish to finish;

  • SF - start to finish.

  • -1/+1 - link lag in days.

In this case:

  • The target of a link is in row 33

  • Start to finish link

  • 0 lag days

Possible problems and solutions

The "Import from file" option is greyed out. 

Scope type dictates whether the option is available. If a Box was created using a Box type with "Own" scope, the option is available. 

Boxes with "Sub" and "None" scopes can't support an import from a file.  

Required fields

Make sure that all fields have been set to "Optional" in the Jira field configuration before importing a file. 

The process of making this adjustment is demonstrated below:

To make things easier, you may copy an existing configuration:

Name it to make things clear for other users:

Click on the field configuration name and change all items to "optional" within it:

Add a new field configuration scheme:

Make sure that the correct field configuration is associated with the scheme:

Go to the Jira project that is added to the Box scope (the project Jira issues will be copied to):

Find the field configuration:

Change the scheme:

Mapping task assignee

By importing from .mpp files, the system maps information about Task assignees, so imported values are correct.

To make sure the Assignee value is imported correctly, double-check if the value in the "Resource Name" field in the MPP file is the same as the value in the user's Full Name field in Jira (case of characters will be ignored).

If there is no user match, the Assignee the field will be set to "Unassigned".

Once the file is imported, the application will not create strong dependencies if the circular dependency is identified (circular dependencies also include parent dependencies). 

  • Link with missing ID

  • Missing Parent Task ID

Period check failure

The start date is later than the end date.