For Jira cloud, there is now a marketplace add-on called Deep Clone for Jira that allows to clone issues with embedded content like watchers.

Disclaimer: I'm the product manager of this add-on.

I'd like to vote on this feature, but I can't. Is this because it's closed? If so, how does Atlasssian determine "issues that resonate the most with our users" if it doesn't allow voting on closed features?

Thanks for taking the time to raise this issue.

Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com

Thanks all.

I've just remembered that this request actually relates to a larger request here: JRA-1558.
Please feel free to comment on that issue with your needs.
I've already linked up the two issues.

Cheers,
Roy

Also would really like to see this happen. Our support team uses a special Support project to track requests that come to their team. If it's something engineering wants to act on, we clone the ticket into the Dev project.

We're really like cloning to copy the watchers (so that the people who cared about the support ticket get notified about changes to the new ticket), aas well as cloning to copy the comments. I'd suggest you revisit the priority of this.

Hello Roy,

I'd like to suggest to re-open this request. I agree with Jonathan that this would be very useful. Coming from MKS, I feel that Jira makes it needlessly difficult to split stories.

When creating multiple stories under the same epic (via the clone function) the watchers list is typically the same. The way Jira currently works, I have to manually add watchers one by one. This consumes time and is prone to error. I'd appreciate it if you reconsider this request.

Thanks in advance and best regards,

Oren B.
SafeNet

Hi Jonathan,

We're trying to be more proactive with the requests we get from our customers by giving them a straight up honest answer that we won't implement something. We think this is a better strategy than having lots of open requests that sit around doing nothing leaving customers wondering what is going on with those requests.

Again, thanks for your feedback.

Cheers,
Roy

If this feature isn't going to be implemented any time soon, should it be in the backlog instead of being closed with won't fix?

Hi Jonathan,

Thanks for your request, however at this time we don't expect to implement this feature.

Cheers,
Roy