|
| 1 | +--- |
| 2 | +title: Using GitHub Copilot to create or update issues |
| 3 | +shortTitle: Use Copilot to create or update issues |
| 4 | +intro: Use {% data variables.product.prodname_copilot_short %} to quickly generate structured, high-quality issues from natural language or images, without filling out every field manually. |
| 5 | +versions: |
| 6 | + feature: copilot-create-issues |
| 7 | +redirect_from: |
| 8 | + - /copilot/using-github-copilot/using-github-copilot-to-create-issues |
| 9 | + - /copilot/how-tos/github-flow/using-github-copilot-to-create-issues |
| 10 | + - /copilot/how-tos/github-flow/use-copilot-to-create-issues |
| 11 | + - /copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues |
| 12 | + - /copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-or-update-issues |
| 13 | +contentType: how-tos |
| 14 | +category: |
| 15 | + - Author and optimize with Copilot |
| 16 | +--- |
| 17 | + |
| 18 | +> [!NOTE] |
| 19 | +> This feature is in {% data variables.release-phases.public_preview %} and subject to change. |
| 20 | +
|
| 21 | +{% data variables.product.prodname_copilot_short %} can create or update issues from a natural-language prompt or a screenshot. It fills in the title, body, labels, assignees, and more—using your repository's issue forms or templates when available. Review and refine every draft before you submit. |
| 22 | + |
| 23 | +## Create an issue |
| 24 | + |
| 25 | +{% data reusables.copilot.access-chat-instructions %} |
| 26 | +1. In the prompt box, describe the issue you want to create. Use `repo-owner/repo-name` to target a specific repository. |
| 27 | + |
| 28 | + For example: |
| 29 | + |
| 30 | + * {% prompt %}In OWNER/REPOSITORY, create a feature request to add fuzzy matching to search.{% endprompt %} |
| 31 | + * {% prompt %}Log a bug for a 500 error. This happens consistently when I try to log into the site.{% endprompt %} |
| 32 | + * {% prompt %}Create a task to change the application logo background to red and add the label "needs design review".{% endprompt %} |
| 33 | + |
| 34 | + > [!NOTE] You can only create issues in repositories where you already have permission to do so. |
| 35 | +
|
| 36 | +1. Optionally, paste, drag, or attach an image to your prompt. Add text to describe the issue, for example: `Create an issue because this error appears when trying to reset a password.` |
| 37 | + |
| 38 | +1. {% data variables.product.prodname_copilot_short %} drafts an issue with a suggested title, body, and metadata (labels, assignees, issue type). If your repository has issue forms or templates, {% data variables.product.prodname_copilot_short %} maps your prompt to the relevant fields. |
| 39 | + |
| 40 | +1. Review the draft. Edit any field, choose a different template, or ask {% data variables.product.prodname_copilot_short %} to make changes with a follow-up prompt. |
| 41 | + |
| 42 | +1. Click **Create**. |
| 43 | + |
| 44 | +## Create multiple issues |
| 45 | + |
| 46 | +If your prompt includes multiple tasks or bugs, {% data variables.product.prodname_copilot_short %} drafts each one separately. |
| 47 | + |
| 48 | +For example: {% prompt %}In OWNER/REPOSITORY, create 3 issues: 1) DETAILS OF ONE TASK, 2) DETAILS OF ANOTHER TASK, 3) DETAILS OF A THIRD TASK{% endprompt %} |
| 49 | + |
| 50 | +Review and edit each draft individually, then click **Create** to publish. |
| 51 | + |
| 52 | +## Create sub-issues |
| 53 | + |
| 54 | +{% data variables.product.prodname_copilot_short %} can break a task into a parent issue with sub-issues. |
| 55 | + |
| 56 | +For example: |
| 57 | + |
| 58 | +`In octo-org/octo-repo, plan a new user dashboard. Break it down into an epic, and create sub-issues for each main feature and task.` |
| 59 | + |
| 60 | +{% data variables.product.prodname_copilot_short %} generates a draft issue tree with a parent issue and sub-issues beneath it. Expand or collapse sub-issues, edit details, and use follow-up prompts to add or remove sub-issues. |
| 61 | + |
| 62 | +When you're ready, click **Review and create**, then click **Create issues**. |
| 63 | + |
| 64 | +## Update an existing issue |
| 65 | + |
| 66 | +Prompt {% data variables.product.prodname_copilot_short %} to modify an issue that already exists. For example: |
| 67 | + |
| 68 | +`In octo-org/octo-repo, update issue #123 to add more details about the bug and steps to reproduce it. Also, change the label to "bug" and assign it to @username.` |
| 69 | + |
| 70 | +Review the draft in the workbench, then click **Update**. |
| 71 | + |
| 72 | +## Link to existing parent or sub-issues |
| 73 | + |
| 74 | +{% data variables.product.prodname_copilot_short %} can connect new issues to ones that already exist. For example: |
| 75 | + |
| 76 | +* `Create a sub-issue for octo-org/octo-repo issue #456.` |
| 77 | +* `Create a parent issue for octo-org/octo-repo issue #456.` |
| 78 | +* `Create a parent issue for octo-org/octo-repo issues #456, #457, and #458.` |
| 79 | + |
| 80 | +Review the draft in the workbench, then click **Review and create** > **Create issues**. |
| 81 | + |
| 82 | +## Assign an issue to {% data variables.product.prodname_copilot_short %} |
| 83 | + |
| 84 | +With {% data variables.copilot.copilot_cloud_agent %} enabled, you can assign an issue to {% data variables.product.prodname_copilot_short %} during creation. See [AUTOTITLE](/copilot/concepts/agents/cloud-agent/access-management). |
| 85 | + |
| 86 | +* **Natural language:** Include `Assign this issue to {% data variables.product.prodname_copilot_short %}.` in your prompt. |
| 87 | +* **Manually:** Select "{% data variables.product.prodname_copilot_short %}" from the assignee list. |
| 88 | + |
| 89 | +{% data variables.product.prodname_copilot_short %} starts working on the issue automatically after creation. |
| 90 | + |
| 91 | +## Further reading |
| 92 | + |
| 93 | +* [AUTOTITLE](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) |
| 94 | +* [AUTOTITLE](/copilot/tutorials/plan-a-project) |
0 commit comments