Issue creation from screenshot/prompt makes template mapping unclear

[AkshatRaj00]

What is the issue about?

Bug report

Which SDK are you using?

Copilot on GitHub / issue creation workflow

What happened?

When creating an issue from a screenshot or natural-language prompt, the generated draft does not always make it clear which issue template was selected or how the prompt was mapped into the template fields.

This makes it harder to verify whether the draft matches the repository’s intended issue format before submission.

What did you expect to happen?

I expected Copilot to make the selected template more explicit and preserve a clearer mapping between the prompt/screenshot and the final issue fields.

Steps to reproduce

1. Open Copilot issue creation flow.
2. Target a repository with issue forms or multiple issue templates.
3. Attach a screenshot or enter a short natural-language prompt.
4. Let Copilot generate the issue draft.
5. Review the generated issue and notice that the selected template or field mapping is not always obvious.

Why this matters

Users may hesitate to submit the generated issue because it is unclear whether the correct issue type/template was selected. This adds friction and reduces trust in the issue creation workflow.

Suggested improvement

• Show the selected template more clearly in the draft UI.
• Make field mapping more transparent before submission.
• If multiple templates are plausible, ask the user to confirm the intended template.

Additional context

GitHub Copilot issue creation is designed to generate structured issues from natural language or screenshots and map prompts into repository issue templates when available. Improving template visibility would make this workflow more reliable.

[github-actions]

Thanks for filing this issue! 🙏

Unfortunately, this issue couldn't be automatically classified because it appears to describe a UX improvement for GitHub Copilot's issue creation flow on GitHub.com (the experience of creating issues from screenshots/prompts in the GitHub UI), rather than a bug or feature request in the copilot-sdk — which is a set of language SDKs (Node.js, Python, Go, .NET) for communicating with the Copilot CLI via JSON-RPC.

This issue may be filed in the wrong repository. If you're reporting feedback about the Copilot issue-creation experience on github.com, you may want to reach out through GitHub Support or file feedback in the appropriate product repository.

A human maintainer will review this issue shortly to determine the right next steps.

Generated by Issue Classification Agent for issue #1249 · ● 99.2K · ◷

[AkshatRaj00]

Thanks for the clarification — understood.

You’re right that this feedback is about the GitHub.com Copilot issue-creation experience rather than the Copilot SDK runtime itself. I opened it here because the workflow is directly related to Copilot-generated issue drafting, but I see that this repository may not be the right place for it.

I’ll treat this as product feedback for the GitHub Copilot issue-creation flow and route it through the appropriate channel / GitHub Support instead.

Thanks for reviewing it!

Thanks for filing this issue! 🙏

Unfortunately, this issue couldn't be automatically classified because it appears to describe a UX improvement for GitHub Copilot's issue creation flow on GitHub.com (the experience of creating issues from screenshots/prompts in the GitHub UI), rather than a bug or feature request in the copilot-sdk — which is a set of language SDKs (Node.js, Python, Go, .NET) for communicating with the Copilot CLI via JSON-RPC.

This issue may be filed in the wrong repository. If you're reporting feedback about the Copilot issue-creation experience on github.com, you may want to reach out through GitHub Support or file feedback in the appropriate product repository.

A human maintainer will review this issue shortly to determine the right next steps.

Generated by Issue Classification Agent for issue #1249 · ● 99.2K · ◷