Improvements to cloning in Jira

[#1]

Hello community, 

I'm Shikhar, a Product Manager in Jira Cloud. Today, I'm thrilled to announce a change that's coming soon. We're making cloning more powerful in Jira by adding new capabilities.

Why we’re making this change

We’ve heard your feedback, and want to give you greater control when you’re cloning work items.

What’s new?

You’ll now be able to clone comments, modify the reporter or assignee, and clone child items in epics.

Feedback Welcomed!

We are continuing to invest in this experience and would love your feedback to make it even better. Here are some ways you can give us feedback:

• Leaving a comment below.

• Opening an issue and selecting Give feedback in the top right.

• Emailing me at spahadia@atlassian.com.

We’d love to hear how we can help you.

[Jimi Wikman]

Good stuff @Shikhar Pahadia !

That is a great way to start my Monday with this good news!

[Milad S_]

Hi @Shikhar Pahadia

This is indeed great news.

I just did a quick test, and it appears the improved clone does copy the child issues; however, it does not copy the subtasks of those child issues. It would be great if you could also add an additional checkbox for the subtask so that if the user selects it, the system also copies grandchild issues. 

We have a requirement for a few non-technical teams that they need to repeat a process a few times throughout the year, and we rely on A4J to copy the epic along with the tasks and their subtasks.

[Elena Lurye]

Hi @Shikhar Pahadia ,

This is a great news, but I would like to share a feedback I received from a client we just complete a Change Management implementation for.

They are looking for a way to clone change requests from the portal (if similar change needs to be submitted).
Can this be implemented?