Clone/Duplicate an Issue

[Archdoog]

Hello, we're using issues and projects across three closely related repositories. We would love the ability to simply clone/duplicate an issue, then potentially transfer it to a different repo with the existing transfer.

Thanks!

[drone1]

Would also really like this, for splitting a larger issue into smaller issues, or more generally just being able to more quickly create tasks that will populate a particular view & sub-view board column.

[drone1]

Hey, are there plans to do this? It is incredibly cumbersome adding tasks to a view at the moment.

For example, my current view shows tasks for my next milestone. Simple, right? However, after typing the task title I have to click Open Item, then Convert to Issue, then Add a milestone, then Add an assignee. Finally, I have a task for my current view, however it took way too many steps.

Adding a simple 'clone' function would save me -- and I'm guessing many people trying -- a lot of time.

I'm sorry to say it but it feels like whatever team is working on this project simply isn't actually using it.

Thanks.

[fgnievinski]

related: google/github-issue-mover#133

[drbilo]

• 1

[wvmitchell]

Just want to +1 this

I have a series of "template" drafts that I work off of in a project so that I can create similar issues across several different repositories. Unfortunately, the only way that I can actually use them is to manually copy all the markdown into a new issue. If I could just duplicate it, I'd probably save ~1-2 mintues per issue I create for my team. That really adds up.

[mgslone]

Would really love to have this. We have weekly processes that I have to copy/paste into new issues for each week. I have to copy over the title, description, tags, priority, and story pointing separately, which seems unnecessarily complicated..

[jdshkolnik]

Duplicating an existing issue is a necessity.

[smassoni-usds]

Would also love to see this. For similar reasons. Given the issue templates don't play nice with the new Projects, it would be nice to be able to easily duplicate issues we keep around as templates vs copying and pasting a bunch of information.

[Chris-Petty]

In a large project with many labels for many subcontexts, often I'm churning out issues that all need the almost the same labels, milestone and project. Configuring an issue template for every combination of labels would be really bad though!

A duplicate button that allows me to create a new issue (in editing state) with the same details would help me a lot; description, assignee, labels, milestone, project...

[MikkelVase01]

+1 Please fix it

[darrenmudd]

Please give us this

[jmaguero]

+1, plzzzz! :D

[mikimer]

+1

[nwoottonsky]

+1

[jayeshkataria]

plus one, this is needed please 🙏

[NJ-G]

+1

[jwdraut]

+1

[oscarvgg]

+1

[sonni-dev]

+1

[hilehman]

+1

[Yorisoft]

+1

[ValeriyFromUA]

+1

[agenteo]

It’s frustrating that in 2025 GitHub Projects still doesn't support cloning issues. In many workflows—especially for backlog or sprint planning—it’s common to start with a larger issue and break it down as we refine the backlog. Without cloning, we have to manually copy paste and MANUALLY copy any tags assigned for each.

Error-prone and inefficient.

[esskar]

+1

[labudis]

Hey all 👋 I'm the Senior Product Manager working on Issues and I have good news that we've started experimenting with a feature that allows users to duplicate issues to accelerate issue creation. Watch this space for further updates!

[uo9qsuf]

Great. is there a roadmap for a public beta?

[labudis]

We are currently testing a version of this feature internally and hoping to release it to the public in the next few weeks. Stay tuned!

[augustocesarfmo]

Precisamos disso urgentemente!

[jlrobins]

'Clone issue' that created the new clone with all of the manually settable metadata (project, labels, sprint, milestone, parent, assignees, etc.) but left the primary fields title and description blank would be superior to how Some Other Major Ticket system works. Let the user directly enter those, hit save, and boom, then the clone becomes real.

[devstuff]

I would take it one step further and have the default description be prefilled from the ISSUE_TEMPLATE corresponding to the original issue's issue type (this might require also having an issue type defined in the template syntax).

[BanSimplified567]

+1

[labudis]

We've just shipped the ability to duplicate an issue to any repository 🚀

You can now quickly duplicate any issue 🎉 with the new Duplicate issue option, which appears at the bottom of the right issue sidebar.

Clipboard-20250714-174724-473.mp4

Here’s how it works:

• Click Duplicate issue to open a new issue form prefilled with the original issue’s content. This includes the title, description, assignees, labels, type, projects, and milestone.
• Change the destination repository before creating the duplicated issue, making it easy to copy issues across repositories.
• Edit any details before creating the new issue to fit your workflow.

This feature helps you:

• Reuse issue formats or recurring tasks without manual copy-paste.
• Split large issues into smaller, actionable items.
• Create similar issues across multiple repositories.

Let us know what you think and share your feedback in this discussion 🙌🏻

[silvioana]

Hi! Thank you very much for adding this feature. We would also like to be able to duplicate an issue that contains sub-issues. This would involve duplicating both the parent issue and the child issues as well. Is this something you plan to add?

[labudis]

@silvioana thank you for this suggestion! I can imagine that being valuable but do you have a particular use case that this would unlock for you? I'd recommend starting a separate discussion in the Community to track that feature request.

[silvioana]

Thank you @labudis! Discussion started #167223

[kimallen]

This is great- I wish I'd discovered the feature months ago. I'd like if it also duplicated the relationship (which in my one test it did not).

[RyanEaston-IHC]

Is this functionality available using the gh cli?

[miguelsvq]

Better late than never. El jue, 17 jul 2025, 16:35, Tadas Labudis ***@***.***> escribió:

…

We've just shipped the ability to *duplicate an issue to any repository* 🚀 You can now quickly duplicate any issue 🎉 with the new *Duplicate issue* option, which appears at the bottom of the right issue sidebar. https://github.com/user-attachments/assets/e3d5c3f1-5572-4192-8dd5-cf0d4da64b2b Here’s how it works: - Click *Duplicate issue* to open a new issue form prefilled with the original issue’s content. This includes the title, description, assignees, labels, type, projects, and milestone. - Change the destination repository before creating the duplicated issue, making it easy to copy issues across repositories. - Edit any details before creating the new issue to fit your workflow. This feature helps you: - Reuse issue formats or recurring tasks without manual copy-paste. - Split large issues into smaller, actionable items. - Create similar issues across multiple repositories. Let us know what you think and share your feedback in this discussion 🙌🏻 — Reply to this email directly, view it on GitHub <#8485 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKVDT6XWPEQG7RKFYFBTC33I6YDZAVCNFSM5JP6CWO2U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCMZXHEZDSOJT> . You are receiving this because you commented.Message ID: ***@***.***>