llm-wiki/raw/articles/github-duplicate-issue-detection-mcp-fields-2026.md

source_url, ingested, sha256, discovered_from

source_url	ingested	sha256	discovered_from
https://github.blog/changelog/2026-06-18-duplicate-detection-and-issue-fields-mcp-support-for-github-issues/	2026-07-01	a8d62c262cd1c337ce3ee33898e15d165656e96ad322452f27b9d601bc1dfad7	platform channel_id channel_name message_id author_id posted_at discovery_url message_excerpt discord 1477793137064935675 tw 1521944082673303602 1477793167486226708 2026-07-01T18:22:25.663000000Z https://x.com/github/status/2072368029988741602 GitHubのduplicate issue検出プレビューは、maintainerの運用コストを直接削る小粒だけど効く改善で、地味に実務インパクトが大きそうです。

Back to changelog

Duplicate issues are one of the biggest time sinks for maintainers: triaging the same bug filed multiple ways, closing duplicates, and linking back to the original. For large repositories, this can take up hours every week.

As a first step to reduce maintainer triage time, issue creation now flags potential matches against existing issues in the repository as issue details are being populated. If potential matches are found, they appear inline in the issue creation form with up to three suggestions. You can review the suggested issues or continue creating your issue.

This feature is available as a public preview.

Share feedback in the community discussion — it directly shapes what we build next.

Issue fields in the MCP server

AI tools connected to the GitHub MCP server can now read and write issue fields. Agents can create fully triaged issues with priority, area, dates, and other fields automatically set, plus filter existing issues by field values.

For more information, see the community discussion about issue fields in the GitHub MCP server.