GitHub Projects
lastmod 2026-03-24created 2026-03-094 edits
GitHub Projects custom fields - meaning
Priority
- Indicates the urgency and importance of a task
- Typical values: P0=Critical, P1=High, P2=Medium, P3=Low
- Used to decide which issues to handle first
Size
- Indicates the scope or complexity of a task
- Typical values: XS (very small), S (small), M (medium), L (large), XL (very large)
- Helps estimate effort and plan the team's capacity
- Usually tied to story points in agile methodologies
Estimate
- The expected time or effort needed to complete a task
- Can be expressed in hours, days, or story points
- Helps with sprint planning and resource allocation
- Used for capacity forecasting
Iteration
- The Korean: 스프린트 or development cycle the issue belongs to
- Typical formats: Sprint 1, Sprint 2, or date-based iterations (e.g. "2026-W12")
- Divides work into fixed periods
- Tracks roughly when work will be completed
Start date
- The date work on the issue is scheduled to start
- Used for scheduling and dependency management
- Distributes work appropriately to prevent bottlenecks
Target date
- The date the issue is expected to be completed
- Usually aligned with the end date of the Iteration
- Used for deadline tracking and progress monitoring
- Helps identify at-risk work early
See also
Favorite site
Guides
Best Practices
- Best practices for Projects - GitHub Docs
- All Items · GitHub Public Roadmap
- Backlog · VS Code Editor GPU Renderer
- [Recommended] SIG Dashboard · Workload-aware & Topology-aware Workstream
- Github - ocornut/imgui - refer only to the issues and wiki (it has no Project, but it is worth consulting alongside)
Pages that link here