Import your task templates from tools like MS Project, MS Excel, or a CSV file. To open the import dialog, click the "+" button and select "Import from a file" (keep in mind, import functionality is also available in the Scope module):
File to upload
Next, select the file you want to import. The maximum file upload size is 10MB.
The following file types are supported:
Set parent tasks as...
BigPicture takes into account the order of the issue types from the IssueTypeScheme of the target project (the one associated with the project you are importing issues into).
Epics and sub-tasks are ignored. The Jira default Issue Type Setting is disregarded.
Import scope to...
Select the project used to store the imported tasks. The project needs to exist in advance.
To successfully perform the import, you need a source (a file that is being uploaded) and somewhere to put the tasks (Jira project where the imported issues are created). Tasks are visualized in the App, but they must exist somewhere in Jira itself.
- Use an existing project. You don't have to set up an empty Jira project and can use an existing one. In such cases, new issues will be added to the existing ones.
- You can also easily set up a new, empty Jira project.
- If you wish, you can use an existing Jira project to perform this action ("Create with shared configuration" option). This will result in copying the Jira project setup (permission, notification, issue security, workflow, issue type, issue type screen, field configuration).
Field mapping and imported fields
When importing from CSV or Excel tables, map the required fields:
NOTE: As the imported file is a template, the task details such as Spent time, Remaining estimate (used to calculate progress), and other fields - besides the mapped ones - are not imported by the App.
Make sure to correctly map the following fields:
- Start date
- End date
- Parent row
For example, if you map "start date" to "baseline start date" the import may not work as desired if the "baseline start date" is empty.
XLSX data format
If the xlsx 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.
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, 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 field will be set to "Unassigned".
Circular Link Dependencies:
- Circular links - strong links aren't allowed to create circular dependencies - in the App, they dictate the positioning of tasks, and circular links could potentially create conflicts. For that reason, the circular relationship will prevent the import from being completed.
- Circular parent dependency
- Link with missing ID
- Missing Parent Task ID
Period check failure
The start date is later than the end date.