gantt-chart-visualization

Classify the source first, then map native and custom fields into a normalized model of tasks, dependencies, calendars, and baselines while preserving source IDs. Use Project XML for MS Project and Jira REST or Advanced Roadmaps CSV for Jira, marking inferred fields with confidence notes.

Use enterprise components like Bryntum, DHTMLX, Kendo UI, or Syncfusion when dependency editing, baselines, and scheduling rules are required. For read-only reporting, Highcharts Gantt, Frappe Gantt, or Plotly work well, and D3 or Canvas fits custom or dense renderings.

Avoid Gantt when status flow matters more than dates (use Kanban), when only a few milestones exist (use a milestone timeline), when booking resources without dependencies (use a calendar), or when dates are unreliable but blocker topology matters (use a dependency graph).

Virtualize rows with a single synchronized scroll model, cull bars outside the visible time range, and render dependency links only for visible or selected rows. Use a hybrid HTML grid with Canvas bars and links when DOM cost dominates.

Yes, via Projects v2 GraphQL date and iteration fields, but GitHub issues have no native start/end schedule fields. Milestones are due-date markers only, so avoid inventing task spans and preserve field IDs and provenance.

Date-only exports mixed with datetime APIs cause timezone boundary shifts. Normalize all dates with an explicit timezone policy, fixed locale parsing, and documented inclusive or exclusive finish-date handling before rendering.