- Tasklists are in private beta and subject to change. We have currently paused onboarding to the beta. Tasklists build upon the previous iteration of task lists.
- For the best experience, we recommend adding no more than 50 tasks to a tasklist and no more than 5 tasklists per issue. There is a hard limit of 250 tasks per tasklist and 10 tasklists per issue.
You can add a tasklist to an issue to quickly break down larger pieces of work into subtasks. You can sketch out a draft of your plans, in either Markdown or in the UI, and optionally convert those draft tasks into real issues or add existing issues and pull requests to your tasklists.
When you add issues and pull requests to a tasklist, the tasklist will show metadata associated with the issue or pull request, including any labels applied, the avatars of people assigned, and the open/close state. When you view the issues and pull requests that have been added to a tasklist, GitHub shows which issues are tracking that subtask.
Tasklists add support for hierarchies of issues on GitHub by creating relationships between your issues. You can create parent and child relationships, you can also create multiple levels of hierarchy that accurately represent your project by breaking down tasks into exactly the amount of detail that you and your team require.
You can create a tasklist using Markdown or using the GitHub UI. Regardless of how you created your tasklist, you can edit it using either Markdown or the UI. For more information, see "Creating a tasklist" and "Managing tasks in a tasklist."
Tasklists also integrate with your projects. You can add the "Tracks" and "Tracked-by fields" to your project views to quickly see the relationships between your issues. For information, see "Using projects and tasklists."