Project Page

Use this page to select the Jira project you wish to import.

Several fields are available to help you configure the import.
Field Description
Group Options Select a saved group option set from the drop-down list. This includes all group options you have access to, which may contain settings like resource inclusion and field mappings across projects.
Connection Choose a connection from the list, which displays both the connection name and Jira URL. To edit or create a new connection, use the ellipsis button to open the Add Jira Connection dialog box.
Select Projects Click to select one or multiple projects from the Jira server to import into your active Open Plan project. This displays a dialog box with accessible projects.
Next Proceed to the next page of the Jira import. This button becomes active only after you've selected at least one project to import.

Date Mapping and Status Sync

When importing data from Jira into Open Plan, the system automatically maps target start and end dates from Jira to the early and late dates in Open Plan. This keeps your project timelines accurate and synchronized. Additionally, Open Plan updates each activity's status-Planned, In Progress, or Complete-ensuring consistency between platforms.

Activity ID Generation

New activities imported from Jira are assigned the next available sequential ID in Open Plan. For example, if the last activity is ID 12, the next imported will be 13. Child activities follow a .1 coding structure based on their parent activity (for example, 13.1).

If the project ID contains letters and numbers, activity numbering begins at 1 and increases by one for each new activity (for example, A10 to A11). If the sequence number exceeds the allowed character limit, rather than being truncated, a warning message will display.

Note: Step IDs in Open Plan use the Jira Issue Key (for example ABC-123).

This system ensures consistent and logical activity ID generation aligned with Open Plan's structure.

After import, a JIRA_OP.log file is saved in your Documents folder, containing any errors, field mismatches, backtracked status changes, or missing items. The Jira UID is also preserved, ensuring smooth round-trip updates back to Jira.