Contents:
|
|---|
...
Introduction
...
|
|---|
You can easily import your task templates from tools like MS Project, MS Excel, CSV, or OpenDocument files.
| Info |
|---|
To unlock import features, install BigTemplate from the Atlassian Marketplace. |
Box
...
admins and Jira
...
admins can import tasks from a file. When the
...
...
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):
...
:
Expand the Add task + drop-down menu.
Select Import tasks from file.
...
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" issue type for the imported tasks will be set to the default "Issue Type" issue type in Jira. It is You can also possible to enable the "Convert parent tasks to Jira Epics" option.
...
Import data from MS Excel / OpenOffice
...
The task fields marked with an asterisk are mandatory. Additionally, you can set the relationships between tasks ("Parent Row" 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
...
no issue types are 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
...
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 BigPicture and must exist somewhere in Jira itself.
...
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.
| Expand | ||
|---|---|---|
| ||
|
.png?version=1&modificationDate=1722941614220&cacheVersion=1&api=v2&width=250)
.png?version=1&modificationDate=1722941613854&cacheVersion=1&api=v2&width=250)
.png?version=1&modificationDate=1722941613446&cacheVersion=1&api=v2&width=250)
Now, choose your Jira project from the drop-down menu.
...
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" 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" type column or it is empty, the imported tasks will get the default "Issue Type" issue type as defined for a particular project in Jira.
You can also enable Enable the "Convert parent tasks to Jira Epics" option. As a result, the option to convert parent tasks will be converted to Jira Epics regardless of the issue type they had in the imported file (the . 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.
...
If the .xlsx file has been created by exporting BigPicture data, the file it can be easily used for importimported.
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).
...
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:
...
Possible problems and solutions
The
...
Import from file
...
option is greyed out.
Scope type dictates The scope type dictates whether the option is available. If a Box box was created using a Box box type with "Own" own scope, the option is available.
Boxes with "Sub" and "None" scopes can't support an import from a fileFor boxes with sub and none scopes, the Import from file optionis unavailable.
Required fields
Make sure that all fields have been set to "Optional" optional in the Jira field configuration before importing a file.
The process of making this adjustment is demonstrated below:.
| Expand | ||
|---|---|---|
| ||
To make things easier, you may copy an copy the existing configuration:  Name it to make things clear for other users:
  Add a new
 
  .png?version=1&modificationDate=1722941609057&cacheVersion=1&api=v2&width=600)
 Find the field configuration:  Change the scheme:  
|
.png?version=1&modificationDate=1722941613103&cacheVersion=1&api=v2&width=600)
Mapping task assignee
By importing from .mpp files, the system maps information about Task 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" name field in the MPP .mpp file is the same as the value in the user's Full Name full name field in Jira (the case of characters will be ignored).
If there is no user match, the Assignee the field field will be set to "Unassigned".
Circular link dependencies
...