Jira / Excel Import

Gantt Page Excel Import Feature

The Gantt page in PM3 now supports importing data from Microsoft Excel spreadsheets. This feature allows users to import and populate various PM3 elements, such as:

• Milestones

• Tasks

• Issues

• Agile Stories

• Sprints

LineType Mapping

The import is designed to align with Jira export formats. Each row in the spreadsheet includes a LineType, which determines how it maps to PM3 elements:

Example:
A row with LineType Bug will be imported as an Issue in PM3.

Note: Jira doesn’t export a LineType of Sprint. Instead, Sprints or Milestones are derived based on the context (Task or Story).

Column Mapping (Flexible Import Format)

PM3 imports now support custom column mappings, allowing for more flexibility:

• You can use your own column headings, then map them to expected fields.

• Comes with default mapping sets, which can be cloned and customized.

• Managed via:
  Admin > File Import Mappings

Spreadsheet Flexibility Includes:

• Column names can be customized

• Columns can be in any order

• Optional columns can be excluded

• Extra columns are ignored during import

Data for LineType = Task doesn’t have to originate from Jira's Agile Task page. Any valid source can be used.

Jira Hyperlinks Support

• Jira export files include an ItemKey column, which is a hyperlink to the Jira item.

• This link is imported and can be displayed in the Gantt table by selecting the “Jira Link” column.

• Clicking the link opens the Jira page (if logged in or with a valid session cookie).

Validation Rules for Jira Imports

PM3 tries to validate imports permissively, but certain rules must be followed:

Valid LineTypes:

• Task

• SubTask / Sub-Task

• Bug

• Story

• Epic (ignored)

Mandatory Fields:

• Item ID (Jira Issue ID) – required for all LineTypes

• Name – required for Tasks, SubTasks, and Stories

• Description and RaisedDate – required for Bugs

• Status – must be one of:

  • To Do

  • In Progress

  • Done

  • Backlog
    (if not empty)

Re-importing Jira Files

• Same Plan Re-import: Updates existing PM3 items with changes from the Jira file (e.g., status or date updates).

• Different Plan Import: Treated as separate.
  Updates made in Plan A won’t affect Plan B unless re-imported there too.

The Jira links remain consistent across plans and always point to the original Jira item.