Aller au contenu principal

The Synchronization Model

One of the most important concepts in MSP Planner is the Explicit Synchronization Boundary.

Unlike many tools that silently overwrite data in the background, MSP Planner treats your professional plan as a separate "Thinking Space." This prevents your planning experiments from accidentally disrupting your team's daily work in Jira.

How it Works: The "Push & Pull" Flow​

MSP Planner uses a review-oriented synchronization model. Data only moves between the timeline and Jira when you explicitly trigger it.

1. The "Pull" (Host -> Timeline)​

When you "Pull" data:

  • The app fetches the latest updates from Jira (e.g., a developer changed a task's status or updated the due date).
  • These changes are surfaced as Sync Notifications.
  • You review the changes and decide whether to merge them into your plan.

2. The "Push" (Timeline -> Host)​

When you "Push" data:

  • The app takes the calculated dates and assignments from your professional plan.
  • It updates the corresponding fields in the Jira issues.
  • This ensures that the team's tickets now reflect the approved project schedule.

Why this is better than Automatic Sync​

Automatic synchronization often leads to "Data Flapping," where a planner moves a date and a developer changes it back, creating a loop of updates. By using explicit sync, you get:

  • Safe Experimentation: You can move tasks around to see "What if?" scenarios without changing the actual Jira tickets until the plan is approved.
  • Controlled Communication: You only push changes to the team once the schedule has been vetted by the PMO or stakeholders.
  • Conflict Resolution: If a task was changed in both places, the app flags a conflict for you to resolve manually, ensuring no data is lost.

Sync Status Indicators​

In the timeline grid, you will see Sync Status Icons on linked rows:

  • Synced: The plan and the Jira issue are in agreement.
  • Host Newer: The Jira issue has been updated since the last sync.
  • Local Newer: You have made changes in the plan that haven't been pushed to Jira yet.
  • Conflict: Both the plan and the host have changed.

Pro Tip: Batch Synchronization​

You don't have to sync tasks one by one. Use the Synchronize toolbar to perform a batch operation on all selected tasks or the entire project, ensuring your whole project is aligned in one click.