Field Configuration & Security
To be useful across different organizations, MSP Planner must be flexible. Every Jira project has different custom fields and naming conventions; our platform adapter ensures that the tool fits your specific setup.
Flexible Field Mapping: Connecting to Your Jira
MSP Planner allows you to define exactly which Jira fields drive the timeline's built-in scheduling semantics. This ensures that you don't have to change your Jira configuration to use the tool.
How to Map Your Fields
- Open the Field Management dialog from the toolbar.
- Navigate to the Mapping tab.
- For each built-in timeline field (e.g., Finish Date, Work, Status), select the corresponding Jira field from your project's catalog.
- Click Apply. The timeline will now use these fields for all synchronization and calculations.
Data Type Compatibility
To ensure stable synchronization, the selected Jira fields must match the required data types of the timeline engine:
| Timeline Field | Required Jira Data Type | Example Jira Field |
|---|---|---|
| Start / Finish Date | Date or Date-Time | Target Start, Due Date |
| Work / Effort | Number (Decimal/Integer) | Original Estimate, Remaining Work |
| Status / State | String or Dropdown | Status, Phase |
| Priority | String or Dropdown | Priority, Urgency |
Mapping Precautions
When mapping fields, be mindful of Jira Automation. If you map a timeline field to a Jira field that triggers a workflow (e.g., changing a date triggers a notification to a client), performing a "Push" from the timeline will trigger those automations in Jira. We recommend mapping to "Planning" fields rather than "Operational" fields to avoid noise.
User-Configurable Display
It is important to distinguish between Field Mapping and Field Display.
- Field Mapping: Defines which data drives the scheduling engine (calculates the critical path, resources, etc.).
- Field Display: Defines which data is visible in the grid.
The Host Field Catalog
You can customize your view without affecting the underlying engine:
- Select Columns: Choose which Jira fields (e.g., "Story Points," "Priority," "Custom Field X") should appear in your grid.
- Arrange Layout: Reorder columns to put the most important data front and center.
Read-Only vs. Editable Fields
To protect the integrity of your project data:
- Host Fields: Fields owned by Jira (like the Issue Key) are read-only in the timeline.
- Timeline Fields: Fields owned by the schedule (like Start Date, Finish Date, and Resource Assignments) are fully editable.
Enterprise Security Model
Security is not an afterthought; it is built into the architecture of the app.
Forge Cloud Isolation
MSP Planner is built using the Atlassian Forge framework. This means:
- No External Servers: Your data does not travel to a third-party server.
- Identity Management: Authentication is handled by Atlassian.
- Data Encryption: All data is encrypted at rest and in transit within the Atlassian ecosystem.
Synchronization Boundaries
The "Push/Pull" model serves as a security and quality gate. By requiring explicit synchronization, you ensure that a Project Manager cannot accidentally change a developer's ticket status or date without a conscious review process.
Auditability
Because the app supports baselines and versioned schedules, you have a complete audit trail of how your project commitments have evolved over time.