# GitHub discussion thread to issue with label carryover

> Promote the discussion that found a real product gap into an issue so the maintainer keeps the context and labels instead of retyping the case from zero.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-discussion-thread-to-issue-with-label-carryover/
- Source: [docs.github.com](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue)
- GrowthDex source hub: [GitHub Docs: Creating an issue](/sources/github-docs-creating-an-issue-docs-github-com/)
- Last checked: 2026-06-05T14:05:00Z
- Rarity: rare
- Budget: free
- Channels: GitHub, Community, Product feedback
- Stages: feedback routing, community archive, work intake, maintainer workflow
- Key metric: GitHub carries the discussion body and labels into the new issue when a maintainer uses Create issue from discussion.

## Why this can grow

Some community threads should stay conversational, but the ones that reveal a real bug, request, or workflow break need a cleaner path into delivery. GitHub lets triage-level maintainers create an issue directly from a discussion, and the discussion content plus labels travel into the new issue body. That keeps the public question intact while giving the team a work object with less copy-paste loss. It also teaches contributors that useful discussions do not disappear into a side room. Good threads can graduate into tracked work.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github discussion thread to issue with label carryover can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Community channel.
3. Use the evidence from docs.github.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

GitHub Docs says people with triage permission can create an issue from a discussion, the discussion post is automatically included in the issue body, and existing labels are retained.

## Adjacent tactics in the same lane

- [Ideas category type with topic voting defaults](/growth-ideas/ideas-category-type-with-topic-voting-defaults/) - 2 shared channels, 1 shared stage
- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels
- [GitHub community profile checklist as trust audit](/growth-ideas/github-community-profile-checklist-as-trust-audit/) - 2 shared channels
- [GitHub contributing tab before first PR](/growth-ideas/github-contributing-tab-before-first-pr/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The issue intake should finish the sorting first](/blog/the-issue-intake-should-finish-the-sorting-first/) - community-led growth, support deflection, seo

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.