Skip to main content

​
How It Works

The Gantt chart operates in a two-phase editing model: you make changes in edit mode, and those changes only persist to Polarion when you explicitly click Save. Until you save, all modifications are local to your browser session. This makes the Gantt a natural tool for what-if analysis. diagram

​
Step 1: Enter Edit Mode

Click the Edit button in the Gantt toolbar. Task bars become draggable, and the lightbox becomes available for field editing.
If your Gantt is configured with alwaysedit mode, the chart is always editable and there is no Edit button. In this case, unsaved changes still behave the same way — they are not persisted until you click Save.

​
Step 2: Experiment with Schedule Changes

With the Gantt in edit mode, you can perform any combination of the following:
  • Drag task bars left or right to change start dates
  • Resize task bars to change duration
  • Edit dates in the lightbox for precise adjustments
  • Create or remove dependency links to evaluate cascading effects
  • Move parent tasks to shift entire work breakdown branches
If auto-scheduling is enabled, moving one task automatically recalculates the dates of dependent successors, giving you immediate feedback on the downstream impact of your change.

​
Step 3: Evaluate the Impact

Review the schedule after your changes. Key indicators to watch:
IndicatorWhat to Look For
Task bar colorsRed or orange bars indicate overdue or delayed items
Dependency arrowsRed dotted lines indicate violated dependency constraints
Resource viewOverallocated resources appear highlighted in the resource view
Critical pathIf enabled, critical path highlighting shows which tasks drive the end date
Range conflictsParent tasks with out-of-range children are visually flagged

​
Step 4: Save or Discard

To save your changes: Click the Save button in the Gantt toolbar. All modifications are persisted to Polarion work items. To discard your changes: Reload the page in your browser. The Gantt reloads the original data from Polarion, reverting all unsaved changes.
The Gantt uses a last-save-wins model. If another user saves changes to the same work items while you are in edit mode, your save will overwrite their changes. Coordinate with your team when performing what-if analysis on shared schedules.
Before starting your what-if analysis, save a baseline snapshot. This lets you compare your experimental schedule against the original plan visually, even after saving changes. See Compare Schedule with Baselines.

​
Verification

You should now see:
  • Task bars responding to drag and resize in edit mode without any server communication
  • Dependency links recalculating successor dates in real-time when auto-scheduling is enabled
  • All changes reverting cleanly when you reload the page without saving

​
See Also

KB ArticlesSupport TicketsSource Code
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/impl/ExtendedWorkingCalendar.java
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/Task.java
  • prod-gantt-src/com.nextedy.polarion.gantt.client/cypress/e2e/ganttPreventMovingOutOfParent.cy.ts
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/js/dateConflictDetector.js
  • prod-gantt-src/com.nextedy.polarion.gantt.client/cypress/e2e/range-conflict/afterDragConflict.cy.ts