Synchronize project fields between Meisterplan projects and their linked Jira epics, and specify the update direction for each field. This ensures your projects are always up to date in both tools.
Prerequisites
To synchronize project fields between Meisterplan and Jira, your Jira instance must be linked to Meisterplan.
Required User Rights in Meisterplan
To configure Jira links, your user group must have the Configure permission under Manage > User Groups > Integrations > Connected Tools > Project and Task Management Tools.
To synchronize project fields between Meisterplan and Jira, an Automation User is required. This user must have the following rights under Manage > User Groups:
- Under Integrations > Connected Tools > Project and Task Management Tools, the Configure right
- Under Project and Resource Planning > Edit Projects, at least the Mine option
- Under Views & Scenarios > Scenarios, the Edit Plan of Record right
- Under Project and Resource Planning > Project Fields:
- For synchronization to Jira: Read Only rights for the respective field
- For synchronization to Meisterplan: Edit rights for the respective field
- Under Integrations, the Import Data right
Required User Rights in Jira
You need a Jira API token with permissions for the relevant Jira fields:
- For synchronization from Jira, Read access for the respective Jira field
- For synchronization to Jira, Edit access for the respective Jira field
We recommend creating a Jira service account and generating API tokens with this account.
Configure Field Mappings
For each Jira link, you can define which fields should be synchronized between Meisterplan and Jira.
- Open the relevant Jira link under Integrations > Jira.
- In the Field Synchronization with Jira Epics section, click Add Project Field to Sync and select the desired Meisterplan field:
- Select the Direction of synchronization and map a Jira Epic Field to the Meisterplan field:
- Confirm your selection using the checkmark at the end of the row and save the Jira link.
What Is Imported / Updated
If the value of a field changes in Jira or in Meisterplan, the mapped field in the other tool is updated with the new value, such as a changed date.
If a Jira field is changed to a value that does not exist in Meisterplan, the value is created in Meisterplan and added to the respective field. For example, if the Status field in Meisterplan has the values 'Red', 'Yellow', and 'Green', but the mapped Jira field is set to 'Blue', this value is added in Meisterplan and the field is updated accordingly.
If a Meisterplan field is changed to a value that does not exist in Jira, no update occurs.
When Data Is Imported / Updated
Changes to Meisterplan fields are updated in Jira immediately.
Changes to Jira epic fields are applied to the Plan of Record every night. In addition, a project is also updated when you select it in Meisterplan or click Refresh Data in the toolbar of the Information Panel.
If you adjust the field mapping of a Jira link, the affected fields in both Meisterplan and Jira are updated immediately.
Edit and Delete Field Mappings
To edit a field mapping, hover over the row and click the field you want to change.
To delete a field mapping, hover over the row and click the trash can icon at the end of the row.
Your changes to the Jira link are only saved after you click Apply in the top-right corner.
Fields
Which Meisterplan Project Fields Can Be Selected
You can select the following system fields:
- Actual Allocation Costs
- Actual Benefit Total
- Actual Financial Events Costs
- Actual Time Worked
- Allocation Estimate at Completion
- Approved Budget
- Approved CapEx Budget
- Approved OpEx Budget
- Approved Total Effort
- Connected Tool
- Cost Estimate at Completion
- Deviation of Actual Cost from Plan
- Deviation of Actual Time Worked from Plan
- Deviation of Allocation EAC from Approved Total Effort
- Deviation of Cost EAV from Approvd Budget
- Deviation Status Compared to Connected Tool
- Estimated Benefit at Complation
- Estimated Net Value at Completion
- Finish
- Future Allocations
- Future Allocation Costs
- Future Costs
- Future Financial Events Costs
- Last Booking Date
- Last Changed
- Missing Allocations Compared to Connected Tool
- Percentage of Completion
- Planned Allocation Costs
- Planned Allocation Costs until Last Booking Date
- Planned Allocations
- Planned Allocations until Last Booking Date
- Planned Benefit
- Planned CapEx
- Planned Financial Events Costs
- Planned Net Value
- Planned OpEx
- Priority Score
- Project Key
- Project Manager
- Start
- Status
- Total Planned Costs
You can select all custom project fields of the following field types:
- Currency
- Date
- Single-Select
- Multi-Select
- Number
- OBS Fields
- Resource
- Text (single-line)
- Text (multi-line)
- URL
Which Jira Epic Fields Can Be Selected
You can select all fields of your Jira epic configuration of the following field types:
- Checkbox
- Date Picker
- Date Time Picker
- Label
- Number
- Project Picker (single project)
- Short Text
- Radio Button
- Select List (multiple choice)
- Select List (cascading)
- Select List (single choice)
- URL Field
- User Picker (single user)
- Text Field (read only)
- Version Picker (multiple version)
- Version Picker (single version)
Which Fields Types Can Be Matched
You can only map fields of certain field types to each other. Once you have selected a Meisterplan project field, only Jira fields that can be mapped to that Meisterplan field are displayed in the corresponding row. The following combinations of field types are supported:
| Meisterplan Project Field | Jira Epic Field |
| Date | date picker; date time picker; |
| Single-Select | radio buttons; select list (single choice); version picker (single version) |
| Multi-Select | checkboxes: labels; select list (multiple choice); version picker (multiple version) |
| OBS Fields | select list (cascading); |
| Resource | user picker (single user) |
| Text (single-line) | short text; text field (read only); project picker (single project) |
| Text (multi-line) | short text; |
| URL | URL field |
| Currency | number |
| Number | number |
Default Mappings
When you add a new Jira link, the following field mappings are created automatically:
| Meisterplan-Feld | Jira-Epic-Feld | Editable |
| Name | Summary | The direction can be changed; the mapping cannot be deleted. |
| Finish | Due Date | The direction can be changed or the mapping deleted |
You can delete and edit the default mappings as needed.