Using projects and tasklists

When issues in your project are tracked by tasklists or contain tasklists, you can use them to create views and filters.

In this article

Note: Tasklists are in private beta and subject to change. We have currently paused onboarding to the beta.

When you add tasklists to your issues and view those issues in your projects, you can use the relationships that you defined in your tasklists to customize views, filter items, and navigate through your issues and pull requests.

When you add an issue with a tasklist to a project, the issues and pull requests in the tasklist are not automatically added to the project. To use the "tracks" and "tracked-by" fields, you will need to add all the issues and pull requests that comprise your tasklist to the project. Consider using the auto-add workflow to automatically add issues to your project. For more information, see "Adding items automatically."

When you group a view by "Tracked by", and some tracked issues and pull requests are not part of the project, GitHub will include a note beneath each group with the option to add those missing issues and pull requests.

Using the "tracks" field

The "tracks" field shows the number of the issues and pull requests included each issue's tasklists. For more information about this field, see "About Tracks and Tracked by fields."

Using the "tracked by" field

The "tracked by" field shows the issues with tasklists currently tracking your project's issues. The "tracked by" field can also be used to group and filter views. You can use the filter below to only show issues that are tracked by issue you have specified:

tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"

For example, tracked-by:"octocat/game#4" will show any issues in the project that are tracked by a tasklist in issue #4 in the octocat/game repository.

You can also group a table layout by the "tracked-by" field. This view configuration results in a list of the issues found in tasklists, clearly grouped by the issue they're associated with, which is shown in the header for each group.

You can also combine filters and grouping by filtering your project for just the issues you want to use, and then grouping with the "tracked-by" field. The example below shows how to filter a view by multiple issues:

tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>","<OWNER>/<REPO>#<ISSUE NUMBER>"

For more information about this field, see "About Tracks and Tracked by fields."