Today’s changelog brings you a snappier issue creation flow in projects, the ability to convert checklist items to sub-issues, required fields on private repositories, and important updates on tasklist blocks and single issue templates.
✍️ Improved issue creation flow in projects
Creating a new issue from a project is now easier than ever. Previously, when you started typing in an issue title in a project, the default was to create a draft issue. However, we’ve heard from user feedback that the primary
desired use case is to create an issue instead of a draft. Now, with this update, you can directly create a new issue by pressing Enter or create a draft with Cmd / Ctrl + Enter.
🔒 Required fields on issue forms for private repositories
You can now specify required fields on issue forms in private repositories, which ensures that contributors provide essential information before submitting an issue.
➡️ Convert checklist items to sub-issues
You can now convert checklist items in issues directly to sub-issues, making it easier to turn draft or to-do tasks into actionable work items.
🌇 Tasklist blocks will be retired and replaced with sub-issues
The private preview feature, tasklist blocks, will be retired on April 30, 2025. Your feedback from the private preview has been invaluable, helping us shape the release of sub-issues, the replacement for tasklist blocks.
Sub-issues provide a dedicated section within each issue, making it easier to track related work without relying on Markdown. You can manage up to eight levels of hierarchy within a single issue and monitor progress directly in your projects.
Migrate to sub-issues
We recommend migrating your tasklists to sub-issues before the retirement date.
To migrate, first simply remove the tasklist Markdown syntax to display the list as an issue checklist.
- ```[tasklist]
- - [ ] task 1
- - [ ] https://github.com/github/github/issues/123
- ```
+ - [ ] task 1
+ - [ ] https://github.com/github/github/issues/123
Then, use the Convert to sub-issue feature to convert desired issues or checklist items into sub-issues.
After April 30, 2025, remaining tasklist blocks will no longer be rendered and will instead be converted to raw Markdown. The Tracked and Tracked by fields on projects will no longer be available.
🌅 Single issue templates (ISSUE_TEMPLATE.md) will be retired
The legacy ISSUE_TEMPLATE.md feature will be retired on March 30, 2025. As a replacement, we encourage creating an ISSUE_TEMPLATE/ subdirectory in any of the supported folders to store multiple issue templates. You can then use the template query parameter to specify which template should populate the issue body. For more details, see the documentation.
After March 30, 2025, repositories still using ISSUE_TEMPLATE.md will default to a blank issue form, allowing users to start fresh when creating issues.
✨ Additional improvements
On top of the many bug fixes we’ve shipped, we’ve also introduced the following improvements:
- You can now create new milestones directly from the milestone picker in any issue.
- The issue template selection will now be bypassed if only one template is available and the blank issue template is disabled.
- You can now create and edit iteration fields via the ProjectV2 GraphQL API.
- We’ve introduced a move dialog in Projects, allowing you to rearrange items and views with precision. You can move views from a tab’s view options menu, while items can be moved through the row actions menu. This allows users who rely on screen readers, keyboards, and other assistive technology to use projects more accessibly.
✍ Tell us what you think!
Join the discussion within the GitHub Community.
See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the documentation.
