Summary
When creating an issue from Copilot using a screenshot or natural language prompt, the generated draft does not always make the template selection or field mapping obvious.
Expected behavior
- Copilot should clearly map the prompt or screenshot to the correct issue template.
- The draft should preserve the relevant template fields and labels.
- If multiple templates match, Copilot should show the selected template clearly before creating the issue.
Actual behavior
- The draft may feel ambiguous about which template was selected.
- Users can lose confidence in whether the right issue type or fields were applied.
- This makes issue creation slower and more error-prone.
Steps to reproduce
- Open Copilot issue creation flow.
- Attach a screenshot or describe the problem in natural language.
- Let Copilot draft the issue.
- Observe that the selected template / mapping is not always obvious.
Why this matters
This adds friction to issue creation and makes it harder to file accurate issues quickly.
Additional notes
If there are multiple repository issue templates, the UI should surface the selected template more clearly before final submission.
Summary
When creating an issue from Copilot using a screenshot or natural language prompt, the generated draft does not always make the template selection or field mapping obvious.
Expected behavior
Actual behavior
Steps to reproduce
Why this matters
This adds friction to issue creation and makes it harder to file accurate issues quickly.
Additional notes
If there are multiple repository issue templates, the UI should surface the selected template more clearly before final submission.