Skip to main content

​
How Saving Works

When you click the Save button, the Gantt sends all pending task and link changes to the Polarion server. A progress spinner appears during the save operation. If there are no unsaved changes, the save button does nothing. The Gantt tracks unsaved changes across all tasks. Modified tasks are visually marked to indicate they have pending changes. The Save button state reflects whether any unsaved changes exist. diagram

​
Common Causes and Solutions

​
Hidden Dependency Items

The most common cause of save failures is when dependency source items are hidden from the Gantt view, either by item scripts or by exceeding the Max Items limit.
When a dependency source item is hidden by an item script or cut off by the Max Items limit, save operations may fail silently. This issue was fixed in v25.5.0. If you are on an older version, apply the workarounds below.
Workaround:
  1. Increase the Max Items widget parameter to a higher value (e.g., 10000) to ensure all dependency-related items are loaded
  2. Review your item scripts and remove any logic that hides items that are dependency sources
  3. Update to Gantt v25.5.0 or later, which resolves this issue

​
Missing or Invalid Field Configuration

Save failures occur when the configured data mapping fields do not match valid Polarion work item fields:
FieldWidget ParameterCheck
Start dateStart FieldMust be a valid date custom field
End dateEnd FieldMust be a valid date custom field
DurationDuration FieldMust be a valid numeric custom field
ProgressProgress FieldMust be a valid float custom field
ResourceResource FieldMust be a valid field or assignee

​
Workflow Validation Errors

Polarion workflow rules may reject changes if required fields are missing or if the current work item state does not allow modifications. Check the browser console for specific error messages from the Polarion server.
Open the browser developer tools (right-click > Inspect > Console tab) to see detailed error responses from the server. Save errors include the specific Polarion validation message explaining why the save was rejected.

​
Permission Issues

The Gantt requires the Polarion user role for all API operations. If a user has reviewer-only access, save operations will fail. See Troubleshooting Reviewer Access Issues for resolution steps.

​
Session Timeout

Long editing sessions can cause the Polarion session to expire. The Gantt includes a keep-alive mechanism to prevent this, but network interruptions may still cause session loss. If saves fail after a long session, refresh the page to re-establish the session.
The Gantt warns you about unsaved changes when navigating away. Always save your changes before leaving the page or closing the browser tab. Unsaved changes cannot be recovered after a page refresh.

​
Diagnostic Steps

  1. Check the Gantt footer for error indicators (triangle icon with count badge)
  2. Open browser console (right-click > Inspect > Console) and look for error messages after clicking Save
  3. Verify field mappings in widget parameters match actual Polarion custom field IDs
  4. Check user permissions — ensure the user is in the nextedy_gantt_users group
  5. Test with a simple edit — try dragging a single task and saving to isolate the issue

​
Verify

After addressing the identified issue, make a small change (drag a task bar to a new date) and click Save. You should now see the progress spinner complete without errors, and the task’s modified indicator should clear. Refresh the page to confirm the change persisted.

​
See also

Support TicketsSource Code
  • prod-gantt-src/com.nextedy.polarion.gantt/src/com/nextedy/polarion/gantt/model/LoadInfo.java
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/js/functions.js
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/js/commands.js
  • prod-gantt-src/com.nextedy.polarion.gantt.client/cypress/e2e/Rewritten Tests/testGanttCreatePlan.cy.ts
  • prod-gantt-src/com.nextedy.polarion.gantt.client/src/js/nextedy.js