Learn how to easily import Jira data as new Meisterplan projects so that you can start your planning fast, keep projects up to date, and view task level insights directly in the Information Panel.

• Required User Rights
• Importing Projects from Jira
  • Result
  • Import Logic
  • How to Import Actual Time Worked and Milestones

Required User Rights

To import data from Jira, you need to have the following rights:

• Manage > User Groups > Integrations > Import Data
• Manage > User Groups > Integrations > Connected Tools > Project & Task Management Tools > Configure
• Edit rights for the desired scenario or Edit Plan of Record
• Manage > User Groups > Project & Resource Planning > Projects > Add Projects

Importing Projects from Jira

To import any Jira data as individual Meisterplan projects, complete the following steps:

1. In the toolbar of the Portfolio Designer, the List or the Board view, click Add and select Import Projects > Jira:
   
2. Select Link Details:
   1. If this is the first time connecting Jira to your Meisterplan system, you need to:
      1. Enter the Jira URL and authenticate the connection:
         
      2. Select the Jira space:
         
   2. If there already is a Jira link, you must:
      1. Select the link you want to use:
         
      2. Or, add a new link and select the Jira space and name.
3. Click Continue in the top right.
4. Select the projects you want to import. You can choose whether to select from a list of Jira epics or to enter a JQL query.
   1. Select from an list of epics:
      
      Epics or parents are always displayed by their epic name, not by their summary. You can filter the epics by Jira project or epic status using the drop-down controls or type into the search bar to narrow down the number of epics.
   2. Import using JQL:
      
      We recommend to test the query in Jira first to ensure you get the desired result(s).
5. If there is still sample data in your Meisterplan, you can decide whether to delete or keep it.
6. Click Import.

Result

• A link to Jia is created in Meisterplan, unless the link already exists. To further configure the Jira link, see the article Configuring Jira Links.
• The selected Jira epics will be imported as Meisterplan projects and linked to their Jira counterparts. 
• All fields listed in the Jira link under Field Synchronization with Jira Epics will be imported, regardless of the mapping direction. Learn more in the article Synchronizing Fields Between Jira and Meisterplan.

Note: If you rename the Jira issue type Epic, the synchronization with Meisterplan will no longer work, as Meisterplan relies on this specific issue type.

Import Logic

When importing selected epics, stories, and efforts from Jira into Meisterplan, the following logic will be applied:

Importing Parent Elements as Programs

If an imported Jira Epic is assigned to a parent element, Meisterplan takes this hierarchy into account during the import. The parent element is created as a program in Meisterplan, and the imported project will be assigned to that program.

If a matching program already exists in Meisterplan (i.e., there is an existing program in Meisterplan with a program key that corresponds to the Jira parent key), Meisterplan will assign the imported project to that existing program. A new program is created automatically only if no matching program exists.

Resource Assignment and Import

Assignees in Jira are assigned to the newly imported projects in Meisterplan:

• They are either matched to an existing resource in Meisterplan based on the email address, or
• If no matching resource is found, they are added as new resources to the Resource Pool (this requires that the automation user has the Edit Resource Pool and Absences right).

Determining the Start and Finish Date of the Meisterplan Project

The start and finish date of the Meisterplan project are calculated as follows (in this order):

1. If the project in Jira has a start and finish date, these are used.
2. If epic dates are not available, or if story dates fall outside of the epic dates, the earliest start date and the latest finish date of the stories in the Jira epic are used.
3. If a story is assigned to a sprint with a start and finish date, the sprint dates override the story dates.
4. If no epic, story, or sprint dates are available, the Meisterplan project starts on the day of import and ends one month later.

Importing Stories as Allocation Segments

• Stories from Jira are imported into Meisterplan as flexible allocation segments per resource.
• These segments can be viewed in the Portfolio Designer with the Flexible allocation mode.
• The start and finish dates of the flexible segments correspond to the start and finish dates of the respective stories.
• Overlapping segments are automatically summed up.
• Partially overlapping segments are split into multiple segments so that overlapping time periods are correctly aggregated.

Handling Incomplete Stories

• Stories without an assignee in Jira are not imported because they cannot be matched to a resource.
• Stories without dates are added before the finish date of the Meisterplan project:
  • if there is a gap between the project finish date and the end of the last story, or
  • if there is no gap, the project finish date is extended by one month and the stories are added there.
• Stories without effort are imported with an allocation of 0.

This allows you to:

• Visualize Jira tasks in a project's details
• Compare allocations and Jira effort on the project level
• Compare allocations and Jira effort across the portfolio

How to Import Actual Time Worked and Milestones

When importing a project from Jira, you can also import actual time worked and milestones from Jira into Meisterplan. To do so, make sure that:

• you have configured a role and/or resource match and the milestone import in the respective Jira link
• the names (when matching Jira teams and roles) or email addresses (when matching Jira assignees and resources) are identical

Learn more in the article Importing Milestones from Jira.

Learn more in the article Importing Actual Time Worked from Jira.