How to copy all comments with timestamp while cloning an issue?

[Gaurav Gupta]

Hello All,

For our use case, we need to copy the comments while cloning an issue. We are trying to leverage the Automation but have not been successful till now.

Any suggestions to achieve this, especially with native functionality, are highly appreiated.

[Mathieu Lepoutre · Accepted solution]

Hi @Gaurav Gupta 

I'm working as a pre-sales engineer with Exalate.

I will suggest something out-of-the box.
Cloning the issue to another Jira Cloud instance with Exalate, and then you can configure that the comments will get copied over.

The ticket will out-of-the-box be fully bi-directionally syncronized, which means, if a field gets updated on either side, it will automatically update on the other side, you can change this to make it uni-directional if you so please.

Exalate is easy and straightforward to set-up and you can control exactly which data you want to send and/or receive. 

If you would like to see a customized demo of the product, please book a slot with us. 

Cheers

Mathieu Lepoutre

[Gaurav · Accepted solution]

Hello @Gaurav Gupta 

Apart from the above suggestions, Automation can be leveraged to create something similar.

Please find below the snapshot of the rule we created for a similar use case. This brings all comments from the original issue and publishes them separated by dashes and blank lines with the author and timestamp.

The code snippet for comment uses smart values and is as:

{{#destinationIssue.comments}}
Comment by: {{author.displayName}} at: {{created}}
{{body}}
------------------------

{{/}}

Let me know if this helps.

--GG

[Gaurav]

@Gaurav Gupta Just to add, the automation fails if the overall length of the comment is more than 32767 characters. This is the default maximum length allowed for comments. There are open tickets with Atlassian to handle this scenario.

[Nic Brough _Adaptavist_ · Accepted solution]

To answer the main question, no, you can't do this with plain off-the-shelf Jira.  It's not something cloning is actually for, so there's no functionality in the cloning bit, and Jira expects different issues to be there for different reasons, and not have comments be copied because they are separate issues with their own life cycles.

You'll need an app to implement this, and Mathieu has already talked about one of the ones I would suggest.