Copy comments from original issue to cloned issue

[jankajeriksen (gmail)]

I have tried different things, to copy ALL comments as new comments to cloned issue for GDPR purposes.

I get the original issue with this (and it works) 

The problem is that it creates the comments as this:

Comment by: Jan Eriksen (jankajeriksen), Jan Eriksen (jankajeriksen) at: Wed Dec 18 09:50:52 GMT 2024, Wed Dec 18 09:51:01 GMT 2024
komm1ntar 1, kommentar 2 in one comment

I would like it to show as

Comment by: Jan Eriksen (jankajeriksen), at Wed Dec 18 09:50:52
komm1ntar 1

Comment by: Jan Eriksen (jankajeriksen), at Wed Dec 18 09:51:01
kommentar 2 

in seperate comments
Anybody know how?
Kind regards Jan

[Clara Belin-Brosseau_Elements]

Hello @jankajeriksen (gmail)

If I understand correctly, you’re trying to copy all the comments to the cloned issue, right?

In that case, I can suggest trying our app Elements Copy & Sync. It allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc). Comments can be cloned and also synchronized between the two issues if needed.

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users).

[Luka Hummel - codefortynine]

Hi @jankajeriksen (gmail) and welcome to the community!

To achieve your goal of copying all comments as separate entries during the cloning process, our app Deep Clone for Jira offers a powerful solution. Deep Clone allows you to clone issues with all their details, including comments, attachments, and other issue data. Moreover, comments are preserved individually, maintaining the original structure.

You just need to check the Comments option under Clone additional fields when configuring the clone.

You can also read more on that feature here.

[Bill Sheboy]

Hi @jankajeriksen (gmail) -- Welcome to the Atlassian Community!

First, copying comments during issue cloning is not supported by built-in features.  Workarounds including using marketplace addons or automation rules (with some limitations).

Next, would you please explain your scenario?  The rule you show will attempt to:

• iterate over the issues in the scheduled trigger
• find the issues listed an a field within that trigger issue (i.e., "Cloned from issue")
• advanced branch over ????  It is unclear what the advanced branch iterates over.
• add a comment to the trigger issue

To use automation rules for comment copying, please see this knowledgebase article for guidance: https://confluence.atlassian.com/jirakb/how-to-copy-comments-from-the-original-issue-to-the-cloned-issue-1236601599.html

Note this will copy the comments, adding them one by one, with the current date / time, and in no particular ordering.  The reason is the advanced branch processes in parallel and asynchronously over the items, and the original order is not enforced.

Finally, this approach may show errors in the copied comments when there were images or other attachments in the comments.  To solve that, the attachments must also be copied.  For the rule you show, that likely will not be possible to fix as the issues are found in a lookup and trigger issue is the one you wanted to update. Please see the workaround in the defect for more information: https://jira.atlassian.com/browse/AUTO-723

Kind regards,
Bill

[Atlass Monster]

Not sure exactly how but here is plan:

Make a list of the comments and for each of value of the list make a comment.

Here are some starting points:

- REST API route https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-comments/#api-group-issue-comments

- Messing around with Smart values - {{issue.comments.first.body}} will return you the first. Or you can get any comment as far you know how many and how to increment it  {{issue.comments.get(8).body}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/

(Note: My solution is not complete one).

[Jim Knepley - ReleaseTEAM]

Hi @jankajeriksen (gmail), welcome to the community.

Your example doesn't show what value is set to the "{{Comm}}" smart value, but I think you're looking for the "{{issue.comments}}" value.

The syntax is slightly different for smart values that are lists, but it's probably easier than where you're at now.

ref: https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/#Using-smart-values-with-sections-and-lists