Skip to content
English
  • There are no suggestions because the search field is empty.

Automatic Ticket Updates

PROEVER provides an automatic recalculation feature that updates your schedule based on task dependencies and parent-child structures. This prevents manual update errors and ensures your plan is always up to date.

Auto-Schedule for Dependencies

When the schedule of a predecessor task (A) changes, the dates of the connected successor task (B) are automatically adjusted.

  • Chained Updates: If tasks are linked (A → B → C), changing A will trigger updates for both B and C.

  • Maintain Intervals: Tasks will slide while maintaining the original gap (lead/lag time) between them.

  • One-Way Sync: Updates only flow from predecessor to successor. Moving a successor task will not affect the predecessor.

  • Multiple Dependencies: If a task has multiple predecessors, the latest possible date that satisfies all dependencies will be applied.

Notes

  • If a user lacks edit permissions for a successor task, the update will fail, and an error notification will be displayed.

  • To ensure system stability, automatic updates will not trigger if a single action affects more than 100 tickets.

 

Auto-Schedule for Parent-Child Relations

This feature automatically recalculates the parent ticket's duration based on its child tickets.

  • Automatic Duration:

    • Parent Start Date = Earliest start date among all child tickets.

    • Parent End Date = Latest end date among all child tickets.

  • The parent schedule is updated instantly when child tickets are rescheduled, created, deleted, or reassigned.

Notes

Even with this setting ON, parent tickets can be moved manually. However, they will be recalculated and overwritten the next time a child ticket is modified.

Schedule Conflict Alerts

If auto-update is OFF or if schedule conflicts occur (e.g., a successor task starting before a predecessor ends) via CSV import, visual alerts will appear.

  • Conflicts are highlighted in red on both the WBS table and the Gantt chart.

  • Even when managing schedules manually, these alerts help you quickly identify unrealistic project plans.

 

Rules and Limitations

  • Dependencies cannot be set between tickets in a hierarchical relationship (e.g., Parent/Child or Grandparent/Grandchild).

  • Automatic updates are disabled during CSV imports to prevent unintended mass changes. Please review conflict alerts and adjust manually after importing.

  • Changes made via auto-update are recorded in the Audit Log and Ticket History under the name of the user who performed the initial action.