This is video 6 of 15 in the Scrum with GitHub Projects series.
← Previous: Prioritizing Your Backlog · Next: Converting Draft to "Real" Issues + Issue Types →
Shameless plug: Already running your team in GitHub Projects? Honest Cheetah adds test management and "when will it be done?" forecasting right inside GitHub, using the data you already have. It measures the system, not the people.
Watch the Video
Or watch it directly on YouTube: Click here
Video Description
I've got to admit. This one was confusing. When you create issues in a GitHub Project, they initially are created as "draft" issues. You'll almost certainly want to convert these issues from "draft" to "real" issues but that also opens up a big can of worms because you have to figure out which Git Repository you want to store those "real" issues.
In this video, I'll take you through the theory behind Draft Issues and my recommendations for how to keep your stuff organized.
BTW, this video was made using SlideSpeaker (https://www.slidespeaker.ai))
Video Info
- Duration: 3:45
- Published: January 29, 2025
Links
Scrum with GitHub Projects: The Full Series
Written series
Video series
- 1. Introduction: Scrum with GitHub Projects
- 2. Create Your First Project
- 3. The Product Backlog
- 4. Requirement Details, Markdown, and Estimates
- 5. Prioritizing Your Backlog
- 6. Demystifying Issues vs. Draft Issues (you are here)
- 7. Converting Draft to "Real" Issues + Issue Types
- 8. Sprint Planning Overview
- 9. Sprint Planning & Creating Iterations
- 10. Sprint Planning: Add User Stories to the Sprint
- 11. Sprint Planning: Creating Tasks with Sub-Issues
- 12. Sprint Planning: The Case of the Missing Sub-Issues
- 13. The Daily Scrum
- 14. Reporting & Charts
- 15. Custom Project Templates
Related:
- What's New in GitHub Projects & Issues (2026 Q4): what GitHub has shipped since this series was recorded
- Agile-ish: Lightweight Project Management with GitHub Projects (VSLive Vegas 2026)
