Scenarios
Safely experiment with project schedules, resources, and task changes without modifying Jira data. Scenarios allow you to create alternative project plans, evaluate different approaches, and synchronize only the approved changes back to Jira.
What are Scenarios?
A Scenario is a temporary copy of your Gantt chart where you can make planning changes without affecting the live Jira data.
Scenarios are ideal for evaluating different project plans before deciding which changes should be applied.
Changes remain isolated until you explicitly synchronize them with Jira.
Note: Creating or modifying a scenario does not change the Live chart or Jira issues.
Common use cases
Scenarios are useful when you need to:
Evaluate different delivery dates.
Rebalance overloaded resources.
Test alternative task assignments.
Delay or accelerate project phases.
Compare multiple planning approaches.
Prepare recovery plans for delayed projects.
Review proposed changes before updating Jira.
Creating a scenario
To create a new scenario:
Click Scenarios on the toolbar.
Select Create Scenario (+).
Enter a name for the scenario.
Click Create.
|
|---|
Once created, the scenario becomes active.
Tip: When working in a scenario, the Scenarios button on the toolbar is highlighted in red, making it easy to distinguish from the Live chart.
You can now freely modify tasks, schedules, resources, and dependencies without affecting Jira.
Working in a scenario
Within a scenario, you can perform the same planning activities as in the Live chart, including:
Moving tasks.
Changing task dates and durations.
Creating or removing dependencies.
Assigning resources.
Adjusting schedules.
Performing resource leveling.
Resolving scheduling conflicts.
All changes remain within the scenario until you decide to synchronize them.
Reviewing changes
Before synchronizing a scenario, you can review every planned modification.
To review changes:
Open the Scenarios menu.
Click the arrow next to the active scenario.
Select Review Changes.
|
|---|
The review dialog lists all pending modifications.
To see detailed changes for a task, click the > (expand) button next to the task.
This allows you to verify every planned update before applying it to Jira.
|
|---|
|
|---|
Synchronizing changes
After reviewing the scenario, you can synchronize the approved changes with Jira.
Only the selected changes are applied to Jira, allowing you to publish updates in a controlled manner.
Once synchronized, the Live chart is updated to reflect the approved changes.
Supported changes
Scenarios support most planning operations, including:
Task scheduling.
Resource assignments.
Task hierarchy.
Task properties.
Dependencies.
Limitations
The following changes are not managed by Scenarios:
Issue status changes
Status updates are saved directly to Jira as soon as they are made and immediately affect the Live chart.
Best practices
Create a separate scenario for each planning option you want to evaluate.
Review all changes before synchronizing them with Jira.
Use scenarios to safely evaluate schedule changes before project milestones or releases.
Test resource balancing and dependency changes without impacting active projects.
Give scenarios descriptive names (for example, Optimistic Schedule, Recovery Plan, or Additional Resources) to make them easier to identify later.