Issue template mapping is unclear when creating issues from Copilot
- 主要语言
- Java
- 星标
- 10.5k
- 派生
- 1.5k
- 平均合并
- 1 天 14 小时
- 30 天内合并 PR
- 129
描述
### 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
1. Open Copilot issue creation flow.
2. Attach a screenshot or describe the problem in natural language.
3. Let Copilot draft the issue.
4. 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.
贡献指南
调研方向
从复现步骤中描述的 Copilot issue 创建流程开始,比较根据屏幕截图、自然语言提示以及包含多个模板的仓库创建的草稿。确定在提交前所选模板和映射字段的呈现位置。完成标准是明确显示所选模板,保留相关字段和标签,并在创建前展示有歧义的匹配结果。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github
- 领域
- design, developer-experience, frontend
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 45/100