Import & Export Mapping
To ensure a seamless round-trip, MSP Planner uses a strict mapping contract. This document serves as a technical reference for how data is transformed as it moves between systems.
The Data Flow
Field Mapping Reference
1. Task Mapping
| Jira Field | MSP Planner Field | MS Project (MSPDI) | Notes |
|---|---|---|---|
| Issue Key | trackerTaskHash | Text30 (Ext. Attr) | Used for identity preservation |
| Summary | name | Name | Primary task identifier |
| Due Date | finish | Finish | Base date for scheduling |
| Story Points | work | Work | Converted based on project settings |
| Assignee | resourceId | Resource Name | Linked via System Resource Hash |
2. Resource Mapping
| System Source | MSP Planner Field | MS Project (MSPDI) | Notes |
|---|---|---|---|
| Jira User ID | systemResourceHash | Resource Text30 | Ensures round-trip re-association |
| Display Name | name | Name | |
| Max Units | maximum_units | Max Units | E.g., 100% -> 1.0 |
Technical Constraints & Rules
The Identity Marker (The Hash)
The core of the round-trip is the Identity Hash.
- When exporting, the app writes a unique hash into a reserved MS Project field (Text30).
- When importing, the app reads this hash to locate the corresponding Jira issue.
- If a row in the import file lacks a hash, it is treated as a Project-only task and created as a local row in the schedule.
Round-Trip Reconciliation
When importing a modified file, MSP Planner does not silently overwrite your data. It uses a Review-Oriented Sync:
- Detection: The app identifies which rows have changed since the last export.
- Review: The user is presented with a diff of the changes.
- Commit: The user explicitly "Pushes" the approved changes into the schedule and then to Jira.
Compatibility Notes
MSP Planner supports the MSPDI (Microsoft Project Detailed Interchange) standard. This ensures compatibility with a wide range of MS Project versions and third-party tools that support the XML-based interchange format.