Zum Hauptinhalt springen

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.

User-Configurable Display​

You are not limited to a fixed set of columns. The timeline allows you to customize exactly what data you see.

The Host Field Catalog​

MSP Planner scans your Jira project to identify available fields. You can then:

  • 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.