Learn how to easily import Jira data as new Meisterplan projects so that you can start your planning fast. We'll let you know where it may be useful to get help from your organization's Jira expert.
- Required User Rights
- Importing Jira Data as Meisterplan Projects
Required User Rights
To import data from Jira, you need to have the following rights:
- Jira Link: To import Jira data, at least one Jira Link must have been added to your Meisterplan system. If a Jira Link has not yet been created in your Meisterplan system, you can learn how to add Jira Links in the Manage Jira Connector article.
- Jira User Account: To access Jira data, you will need a Jira user account. If you don't have a Jira account, contact your internal Jira expert.
- Matching Roles and Resources (optional): If you have configured a role and / or resource match in the Jira link, the efforts in Jira will be imported as allocations in Meisterplan, provided the names (when matching Jira teams and roles) or email addresses (when matching Jira assignees and resources) are identical.
Find out how to test the Jira Connector without risking live data in the Testing the Jira Connector article.
Importing Jira Data as Meisterplan Projects
To import any Jira data as individual Meisterplan projects, complete the following:
Step 1: Click on More Actions in the toolbar of the Portfolio Designer and select Import from Jira:
Step 2: Select the desired Jira link and proceed by clicking Continue:
You may then be prompted to log in to your Jira account. Learn more about this step in the Jira Authorization and Login article.
If the desired instance is not available in the list, click the Add New Jira Link button to link another instance and use that for import.
If you don't have a Jira account or don't know which instance you should use, please ask your internal Jira expert.
In the following dialog, you will select the Jira data you want to import. You can choose whether to select from a list of Jira epics or to enter a JQL query. To switch between those two modes, click Import Using JQL or Import Using Epic List, respectively, in the top right corner of the dialog:
Depending on the selected mode, proceed with the relevant next step.
Step 3a (Select from Epic List): Select the Jira epics you want to import as Meisterplan projects:
Meisterplan displays up to 100 of the epics in the Jira instance configured for the active Jira Link.
You can filter the epics by Jira project or epic status using the drop-down controls or type into the search box to narrow down the number of epics.
If the desired epics are not in the active Jira instance, click Cancel and select a different Jira link in the previous step.
Step 3b (Enter JQL Query): Enter a JQL query:
To import Jira next-gen projects, use "parent" for your query:
We recommend to test the query in Jira first to ensure you get the desired result(s).
Step 4: Once you have selected epics or entered a JQL query, click on the Import Epics or Import button, respectively.
Now Meisterplan creates one or several projects, for which Jira data can be displayed on the right-hand sidebar:
If you would like to import Jira data from multiple Jira instances, simply repeat these steps for each Jira instance you wish to import from.
A new project with the name of the Jira epic or project will be added to Meisterplan.
Start Date and Project Length
When importing next-gen epics from Jira that have a start date and a due date, these dates will be imported along with the project as the start and finish dates in Meisterplan. This only applies when importing using the Epic List, not using a JQL query. If the start date is missing, one month is calculated back from the finish date and this date is entered as the start date. If the finish date is missing, one month is calculated from the start date into the future and this date is entered as the finish date.
In all other cases (e.g., importing using JQL), the following applies:
The start date of the project is the date of the import. The Scheduled Finish Date for imported Jira epics will be set automatically according to the selected zoom level in the Portfolio Designer:
Standard project length in Meisterplan
If you have configured a role and/or resource match in the respective Jira link, the efforts of assignees or teams in Jira will be imported as role or resource allocations in Meisterplan, provided the names (when matching Jira teams and roles) or email addresses (when matching Jira assignees and resources) are identical. The Jira efforts will be converted into allocation values based on the configuration of the Jira link that is used (e.g., effort and velocity).