d42d3e850d
Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
132 lines
6.6 KiB
Markdown
132 lines
6.6 KiB
Markdown
---
|
|
title: About Tasklists
|
|
intro: 'You can use Tasklists to divide your issues into smaller subtasks.'
|
|
versions:
|
|
feature: 'projects-v2-tasklists'
|
|
miniTocMaxHeadingLevel: 3
|
|
redirect_from:
|
|
- /early-access/issues/about-tasklists
|
|
---
|
|
|
|
{% data reusables.projects.tasklists-release-stage %}
|
|
|
|
## About Tasklists
|
|
|
|
Tasklists add support for hierarchies of issues on {% data variables.product.product_name %}, helping you to keep track of your issues, divide your issues into smaller subtasks, and create new relationships between your issues.
|
|
|
|
Tasklists build upon the previous iteration of [beta task lists](/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists), retaining the ability to convert items into issues, display the progress of a Tasklist, and create a "tracks/tracked by" relationship between issues.
|
|
|
|
The issues you add to your Tasklists will be automatically populated to show their assignees and any labels applied.
|
|
|
|
|
|
|
|
### About integration with {% data variables.projects.projects_v2 %}
|
|
|
|
Your project's side-panel displays an issue's place in the hierarchy on a breadcrumb menu, allowing you to navigate through the issues included in your Tasklists. You can also add the Tracks and Tracked by fields to your project views to quickly see the relationships between your issues. For information, see "[About tracks and tracked by fields](/issues/planning-and-tracking-with-projects/understanding-fields/about-tracks-and-tracked-by-fields)."
|
|
|
|
## Creating Tasklists
|
|
|
|
You can create a Tasklist using Markdown in an issue description. Create a fenced code block and include `[tasklist]` next to the opening backticks. You can then preface each item with `- [ ]` and include links to other issues or text. You can optionally include a title as a Markdown header at the top of your list.
|
|
|
|
````
|
|
```[tasklist]
|
|
### Tasks
|
|
- [ ] https://github.com/octo-org/octo-repo/issues/45
|
|
- [ ] Draft issue title
|
|
```
|
|
````
|
|
Your Markdown will be rendered by {% data variables.product.product_name %} as a Tasklist. You can then make changes and add issues and draft issues using the UI. If you edit the issue description, you will be able to modify the Markdown directly or copy the Markdown to duplicate the Tasklist in other issues.
|
|
|
|
You can also click {% octicon "checklist" aria-label="The checklist icon" %} in the formatting toolbar to insert a Tasklist when creating a new issue or editing an issue description.
|
|
|
|
|
|
|
|
## Adding issues to a Tasklist
|
|
|
|
1. At the bottom of your Tasklist, click **Add item to Tasks**.
|
|
|
|
|
|
|
|
1. Select the issue to add to your Tasklist.
|
|
|
|
* To add a recently updated issue from the repository, click the issue in the dropdown, or use your arrow keys to select it and then press <kbd>Enter</kbd>.
|
|
|
|
|
|
|
|
* To search for an issue in the repository, start typing the title of an issue or the issue's number and click on the result, or use your arrow keys to select it and press <kbd>Enter</kbd>.
|
|
|
|
|
|
|
|
* To add an issue directly using its URL, paste the URL of an issue and press <kbd>Enter</kbd>.
|
|
|
|
|
|
|
|
|
|
## Creating draft issues in a Tasklist
|
|
|
|
Draft issues are useful to quickly capture ideas that you can later convert into issues. Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your Tasklist.
|
|
|
|
1. At the bottom of your Tasklist, click **Add item to Tasks**.
|
|
|
|
|
|
|
|
1. Type your draft issue title and press <kbd>Enter</kbd>.
|
|
|
|
|
|
|
|
|
|
## Converting draft issues to issues in a Tasklist
|
|
|
|
You can convert draft issues into issues. Issues are created in the same repository as the Tasklist's parent issue.
|
|
|
|
1. Next to the draft issue you want to convert, click {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
|
|
|
|
|
|
|
1. In the menu, click **Convert to issue**.
|
|
|
|
|
|
|
|
|
|
## Removing an issue or draft issue from a Tasklist
|
|
|
|
You can remove issues and draft issues from your Tasklist. Issues removed from a Tasklist are not removed from the repository.
|
|
|
|
1. Next to the draft issue you want to remove, click {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
|
|
|
|
|
|
|
1. In the menu, click **Remove**.
|
|
|
|
|
|
|
|
## Changing the title of a Tasklist
|
|
|
|
When you create a new Tasklist, the default title is "Tasks." You can modify the title by editing the issue's markdown.
|
|
|
|
1. In the top-right of the issue body, click {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
|
|
|
|
|
|
|
1. In the menu, click **Edit**.
|
|
|
|
|
|
|
|
1. Modify the header in the fenced code block to your new title. For example, change `### Tasks` to `### My new title`.
|
|
|
|
|
|
|
|
1. Click **Update comment**.
|
|
|
|
## Copying a Tasklist
|
|
|
|
When you copy your Tasklist using the "Copy Markdown" option, {% data variables.product.product_name %} copies Markdown to your clipboard and includes the Issue's name so you can paste the Tasklist outside of GitHub without losing context.
|
|
|
|
1. In the top-right of your Tasklist, click {% octicon "kebab-horizontal" aria-label="The kebab menu icon" %}.
|
|
|
|
|
|
|
|
1. In the menu, click **Copy markdown**.
|
|
|
|
|
|
|