Creating GitHub Issues with Copilot

Filing GitHub Issues is usually a context-switching chore — open a tab, pick a template, fill in a title, body, labels, and assignees, then repeat for every item on your list. GitHub Copilot at github.com/copilot eliminates that friction: describe a task in plain language (or paste a screenshot), and Copilot drafts a structured, ready-to-submit issue in seconds. You review, refine, and click Create.

Availability: All GitHub Copilot plans including Free.

Creating a single issue

Go to github.com/copilot and describe the issue you want to create. Use the OWNER/REPO format to target a specific repository; if you omit it, Copilot infers from the last repository you filed an issue in.

Example prompt	What Copilot does
`In acme-org/api, create a feature request to add fuzzy matching to search.`	Drafts a feature-request issue with title, body, and suggested labels for the `acme-org/api` repo
`Log a bug for a 500 error that happens consistently when I try to log in.`	Selects a bug-report template (if one exists), fills in steps to reproduce and expected vs. actual behaviour
`Create a task to update the logo background to red and add the label "needs design review".`	Drafts a task issue and pre-selects the needs design review label

If your repository has issue forms or templates, Copilot picks the best match automatically and maps your prompt text into the right fields — without losing any details. You can switch to a different template at any time without losing your input. If a required field has insufficient context, Copilot asks a follow-up question.

You can also attach an image (paste, drag-and-drop, or the Image button) to generate a visual bug report. Copilot reads the screenshot and builds the issue body around what it sees.

Creating multiple issues from a to-do list

Paste your entire task list into a single prompt and Copilot drafts each item as a separate issue in one pass.

Example: In acme-org/web, create 3 issues: 1) Update Node.js to v22, 2) Fix the broken navbar on mobile, 3) Write end-to-end tests for the checkout flow.

Each draft appears individually in the workbench. Review and edit them one by one, then click Create on each issue you want to publish. You are always in control — nothing is submitted until you confirm.

Input style	Best for
Numbered list in a single prompt	Converting a sprint backlog or meeting notes into tickets in one shot
One prompt per issue	Issues that need custom metadata (assignee, milestone, label) per item
Screenshot attachment	Bug reports where visual evidence speaks louder than words

Creating sub-issues and epics

For larger initiatives, Copilot can generate a full issue hierarchy in a single prompt.

Example: In acme-org/web, plan a new user dashboard. Break it down into an epic and create sub-issues for each main feature and task.

Copilot generates a draft issue tree — a parent epic at the top with sub-issues beneath it. You can expand or collapse sub-issues, click any node to edit its details, and use Review and create to see the full tree before publishing.

You can also modify the tree mid-session:

Remove a sub-issue: Remove sub-issue <NAME> from the issue tree
Add a sub-issue: Add an additional sub-issue with <DETAILS> to the issue tree
Link an existing issue as a parent: Create a parent issue for acme-org/web issue #456.

Once satisfied, click Review and create → Create issues to publish the entire tree at once.

Updating an existing issue

Copilot can also update issues that already exist. Reference the issue by number and describe what should change:

In acme-org/web, update issue #123 to add more detail about the bug and steps to reproduce it. Also change the label to "bug" and assign it to @alice.

Copilot drafts the updated body in the workbench. Review the diff, edit if needed, and click Update to publish the change.

Assigning issues to Copilot

If your organisation has Copilot coding agent enabled, you can assign a newly created issue directly to Copilot in the same prompt:

In acme-org/web, create an issue to fix the broken navbar on mobile and assign it to Copilot.

Once the issue is created and assigned, Copilot starts working on it automatically. A 👀 reaction appears on the issue to indicate it is actively being worked on. You can track progress through the Agents tab on GitHub.com or from any of the seven surfaces described in the Tracking Coding Agent Sessions post.

Permissions and limits

Constraint	Detail
Repository access	You must already have permission to create issues in the target repository. Copilot does not bypass repo access controls.
Preview status	This feature is in public preview and subject to change.
Coding agent assignment	Assigning to Copilot requires Copilot coding agent to be enabled (Pro+, Business, or Enterprise plans).