You will want to use the Gantt chart data in other applications such as Excel, Google Sheets, or Jira.
Gantt Chart Planner for Confluence provides the CSV data export feature to achieve it.

How to export data as CSV

  1. Open CSV export dialog

  2. Select options

  3. Click the Export button. Then, you can download a CSV file.

CSV Export options

Option

Description

Exclude inactive data

Check this option to exclude inactive data from the CSV file.
Inactive data means,

  • Inactive Tasks.

  • Dependencies that connect to inactive tasks.

  • Not active dependencies.

Omit time and adjust end date

Check this option if you want to omit time values for all date columns to use CSV data in the application that doesn’t support time values like Jira.

If you check this option, except for milestone tasks, end date values, including baseline end date, deadline date, and end date constraints, at midnight will be the previous date to keep the actual date.

e.g.

  • Start = 2022-04-07 00:00:00, End = 2022-04-08 00:00:00 will be Start = 2022-04-07, End = 2022-04-07

  • Start = 2022-04-07 00:00:00, End = 2022-04-08 01:00:00 will be Start = 2022-04-07, End = 2022-04-08

CSV file format

Character code

Character code is UTF-8 with BOM.

Row

Each row represents each task.

Columns

Column Name

Description

id

ID of the task. It’s a unique number in the single Gantt chart.

wbsCode

Dot separated number that represents task sequence in the hierarchy.

name

Name of the task.

startDate

Start date of the task.

endDate

End date of the task.

duration

Duration of the task. Please note that the duration unit will be the day unit even if you set other duration units.

Resource **

  • resourceName

  • resourceAtlassianId

  • resourceUnits

Assigned resources.

  • resourceName

    • User name of the assigned resource.

  • resourceAtlassianId

    • Atlassian account id of the assigned resource.

  • resourceUnits

    • Assigned units of the assigned resource.

percentDone

% Done of the task.

constraintType

Constraint type of the task.

  • Must start on will be muststarton.

  • Must finish on will be mustfinishon.

  • Start no earlier than will be startnoearlierthan.

  • Start no later than will be startnolaterthan.

  • Finish no earlier than will be finishnoearlierthan.

  • Finish no later than will be finishnolaterthan.

constraintDate

Constraint Date of the task.

deadlineDate

Deadline Date of the task.

manuallyScheduled

If manually scheduled is enabled for the task, it will be “true”. Otherwise, it will be “false”.

rollup

If rollup is enabled for the task, it will be “true”. Otherwise, it will be “false”.

defaultCollapse

If default collapse is enabled for the task, it will be “true”. Otherwise, it will be “false”.

inactive

If task is inactive, it will be “true”. Otherwise, it will be “false”.

color

Color of the task.

propagateColor

If propagate color is enabled for the task, it will be “true”. Otherwise, it will be “false”.

webLink

Weblink of the task.

note

Note of the task.

milestone

If task is a milestone, it will be “true”. Otherwise, it will be “false”.

baselineStartDate

Baseline start date of the task.

baselineEndDate

Baseline end date of the task.

parentId

Task id of the parent task.

childId **

Task ids of the children.

level

The hierarchy level that the task is in. 1 means the top level.

jiraIssueType

This is for recommended Jira issue type when importing data into Jira.

  • Task hierarchy level = 1 will be “epic”.

  • If the task hierarchy level is larger than two and the task is a leaf task, it will be “subtask“.

  • Others will be “normalTask”.

jiraEpicName

This is for setting epic name field value when importing data into Jira.
It will be the name of the task if the jiraIssueType is epic.

jiraEpicLink

This is for setting epic link field value when importing data into Jira.
It will be the name of the parent task if the task hierarchy level is two.

jiraSubtaskParentId

This is for setting sub-tasks’s parent id when importing data into Jira.
It will be the id of the parent task if the jiraIssueType is subtask.

mainResource

  • mainResourceAtlassianId

  • mainResourceUnits

The main resource is an assigned resource that has the largest units. If multiple resources have the largest units, the resource that has the least alphabetically ordered name will be the main resource.

  • mainResourceAtlassianId

    • Atlassian account id of the main resource.

  • mainResourceUnits

    • Assigned units of the main resource.

predecessors **

  • predecessorFromId

  • predecessorType

  • predecessorLag

  • predecessorActive

Predecessors of the task.

  • predecessorFromId

    • Id of the preceding task.

  • predecessorType

    • Type of the predecessor. ***

  • predecessorLag

    • Lag of the predecessor.

  • predecessorActive

    • If the predecessor is active, it will be “true”. Otherwise, it will be “false”.

successors **

  • successorToId

  • successorType

  • successorLag

  • successorActive

Successors of the task.

  • successorToId

    • Id of the succeeding task.

  • successorType

    • Type of the successor. ***

  • successorLag

    • Lag of the successor.

  • successorActive

    • If the successor is active, it will be “true”. Otherwise, it will be “false”.

** This column is repeated for the count of source properties.

*** Dependency type will be one of the SS, SF, FS, or FF. SS means Start-to-Start. SF means Start-to-Finish. FS means Finish-to-Start. FF means Finish-to-Finish.

How to import CSV data into Jira

You would want to import Gantt chart data into Jira if you plan a project in Confluence, then manage the project in Jira.
Here is how to import CSV Gantt chart data into Jira to use the data with Basic Roadmaps, Advanced Roadmaps, or third-party Gantt chart apps like WBS Gantt-Chart for Jira.

To import CSV data into Jira, you use the CSV import feature of Jira.

Steps to import CSV data into Jira

Please watch the demo video to see the details.

Export CSV data from Gantt Chart Planner

  1. Open the Gantt chart you want to export the data.

  2. Open CSV export dialog. And check “Exclude inactive data“ and “Omit time and adjust end date“.

  3. Click “Export“ and download the CSV file.

Import CSV data into Jira

  1. Select Filters > Advanced issue search.

  2. Click more ( ••• ) > Import issues from CSV.

  3. Choose the exported CSV file. If you have imported other Gantt chart CSV data and downloaded the configuration file, check the “Use an existing configuration file” and upload the configuration file. Then, click “Next”.

  4. Fill out the form, then click “Next“.

    1. Import to Project → Select the project you want to import the Gantt chart data.

    2. File encoding → UTF-8

    3. Delimiter → “,”

    4. Date format → “yyyy-MM-dd“

  5. Map CSV fIelds to Jira fields, then click “Next“.
    See the Field mappings section below to find how to map them.

  6. Map CSV field values to Jira field values, then click “Validate“.

  7. Check if no errors and warnings are found.
    Please ignore “Parent Issue cannot be null“ errors.

  8. Click “Begin Import“.

  9. Check if no errors and warnings are found.

  10. If you download the configuration file, you can skip the field mappings by using the file in the future importing.

Field mappings

There are two ways to construct WBS in Jira. You have to select which way you use.
Field mappings from CSV fields to Jira fields depend on which way you select.

  1. Epic/Story/Sub-task hierarchy

  2. Issue link hierarchy

Method

Pros/Cons

Supported by

Epic/Story/Sub-task

  • Basic Roadmaps

  • Advanced Roadmaps

  • Third-party apps supporting this method like WBS Gantt-Chart for Jira.

Issue link

Opposite of the above.

  • Third-party apps supporting this method like WBS Gantt-Chart for Jira.

Field mappings to use epic/story/sub-task hierarchy

CSV column

Jira field

Map field value

Note

jiraEpicLink

Epic Link

No

jiraEpicName

Epic Name

No

jiraIssueType

Issue Type

Yes

Field value mappings should be,

  • epic → Epic

  • normalTask → Any issue type of neither epic nor sub-task issue types

  • subtask → a sub-task issue type

jiraSubtaskParentId

Parent Id

No

Field mappings to use issue link hierarchy

CSV column

Jira field

Map field value

Note

childId

Issue link for hierarchy

No

  • WBS Gantt-Chart for Jira

    • Hierarchy link (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

If direction of the hierarchy issue link is from children to parent, use parentId CSV column instead.

level

Issue Type

Yes

Common field mappings

The table below shows the mapping of fields that are not related to the representation of the hierarchy.

CSV column

Jira field

Map field value

Note

id

Issue id

No

name

Summary

No

note

Description

No

mainResourceAtlassianId

Assignee

No

startDate

Field for start date

No

  • Basic Roadmaps

    • Start date

  • Advanced Roadmaps

    • Start date **

  • WBS Gantt-Chart for Jira

    • Start date (WBS Gantt-Chart) ***

  • Other Third-party apps

    • Depends on apps

endDate

Field for end date

No

  • Basic Roadmaps

    • Due date

  • Advanced Roadmaps

    • Due date **

  • WBS Gantt-Chart for Jira

    • Finish date (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

deadlineDate

Due Date

No

Only when Due Date isn’t mapped with endDate.

successorToId

Issue link for hierarchy

No

  • Basic Roadmaps

    • Link “Blocks“

  • Advanced Roadmaps

    • Link “Blocks“ **

  • WBS Gantt-Chart for Jira

    • Finish-to-Start link (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

If direction of the dependency issue link is from the succeeding task to the preceding task, use the predecessorFromId CSV column instead.

baselineStartDate

Field for baseline start date

No

  • WBS Gantt-Chart for Jira

    • Baseline start date (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

baselineEndDate

Field for baseline start date

No

  • WBS Gantt-Chart for Jira

    • Baseline finish date (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

mainResourceUnits

Field for work assignment ratio

No

  • WBS Gantt-Chart for Jira

    • Units (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

manuallyScheduled

Field for manually scheduled

Yes

  • WBS Gantt-Chart for Jira

    • Manually scheduled (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

milestone

Field for milestone

Yes

  • WBS Gantt-Chart for Jira

    • Milestone (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

percentDone

Field for progress

No

  • WBS Gantt-Chart for Jira

    • Percent done (WBSGantt) ***

  • Other Third-party apps

    • Depends on apps

** It’s for default settings. It depends on the configuration of Advanced Roadmaps.

*** It assumes WBS Gantt-Chart for Jira’s issue configuration is below. Please see this document for details.

FAQ about importing CSV into Jira

Question

Answer

Epic links are not created for team-managed-projects.

In team-managed-projects, epic link can’t be created by CSV importer. So, you have to link tasks with epics manually after importing. https://jira.atlassian.com/browse/JSWCLOUD-17758.

Epic links aren’t created because of “The value [ [Summary] ] can't be added to the Custom Field [ Epic Link ]. The value [ [Epic Name] ] can't be found or is in the incorrect format“ error.

This error occurs when the epic that has the same epic name already exists in the target project.
Please link epics manually or re-import the CSV file after ensuring unique epic names.

Can’t find Jira fields in field mappings

Jira fields to map have to be placed on create issue screen of the issue types you create.

https://confluence.atlassian.com/jirakb/missing-fields-for-mapping-when-importing-issues-through-csv-in-jira-720420577.html