Create GitHub Project Insights Charts
Create Insights charts that answer a delivery question using project items as their data. Check archive and deletion effects before interpreting historical progress.
Step-by-step guide
Check access and scope
You need access to the project and permission to manage charts. Choose a stable measurement scope and check current versus historical chart availability.
Choose the chart question
Open project Insights and choose the appropriate chart type.
Configure chart scope
Set field, aggregation and filter scope.
- Worked example: A chart of upcoming work by iteration can reveal overloaded windows. It cannot prove capacity unless effort and ownership data are maintained, so inspect large or unassigned issues separately.
Compare source items
Compare chart counts with representative project items.
Audit archive coverage
Inspect whether archived or deleted work affects coverage.
Explain reporting limits
Share the interpretation with its scope and known gaps.
Verify the result
The chart agrees with sampled items and the review notes explain the measured population.
Common mistakes
Check the handoff edge case
A count by iteration does not measure capacity without consistent effort and ownership data. Keep that limitation in the interpretation.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.