Insiders Feedback: GitHub MCP App retains completed issue creation form after submission
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- ai-infra-agents, frontend
Research direction
The payload names no files, functions or tests, so the first step is to reproduce it: ask the GitHub MCP App to create an issue, submit the form, then return to the same session. The issue does not show whether the form state lives in the MCP server (this repository, github-mcp-server) or in the Copilot host UI, so confirm that before looking for code. Done means the form is dismissed or cleared after a successful submission, and a reopened session does not show it again.
Written by the indexing model from the issue text.
Description
Version: Insiders
Feature: GitHub MCP App
Feedback: After asking GitHub Copilot to create a GitHub Issue, the issue creation form appeared as expected with the generated issue details. I reviewed the information and clicked Create Issue, and the issue was successfully created.
However, after returning to the same session, the issue creation form appeared again, still displaying the previously generated issue details and waiting for a response to create the issue.
The issue creation functionality itself works perfectly, and I can continue interacting with Copilot normally, including sending new prompts. However, the previously completed issue creation form remains visible instead of being dismissed or cleared after successful submission.
I'm not entirely sure if this is an actual bug or an expected behavior, but I wanted to share this observation in case the form state is not being properly reset after a successful action.
- Dominant language
- Go
- Stars
- 34.2k
- Forks
- 5.3k
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3760 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/github-mcp-server#3758 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3729 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3722 ·
Maintainers usually reply within 2 days
-
Insiders Feedback: PR created UI doesn't link to the PRPossibly taken @genius-0963 claimed this 5 days ago. Openbug insiders user-experience
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3658 ·
Maintainers usually reply within 2 days
All issues in github/github-mcp-server
Similar issues
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hexlet-basics/hexlet-basics#962 ·
Maintainers usually reply within 1 day
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransportPossibly taken @dejanstrbac claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
renovate-health
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-network-latency-exporter#267 ·
Maintainers usually reply within 1 day
-
Network capture does not workPossibly taken @KSpaceer claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aquasecurity/tracee#5395 ·