Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copy comments while cloning the Issue in Jira cloud

Can we copy comments while cloning the Jira issue in cloud

5 answers

You can create an automation that is triggered on issue link > then look for {{destinationIssue.comments}} (this looks for the issue that yours is cloned from) > use an advanced branch to iterate over each comment and >  then add the comments one-by-one to the cloned issue. 

I used these articles to help me get here:


Screen Shot 2022-11-01 at 4.12.42 PM.png

Screen Shot 2022-11-01 at 4.13.05 PM.png

Screen Shot 2022-11-01 at 4.13.19 PM.pngScreen Shot 2022-11-01 at 4.13.30 PM.png

The branching shown in this example collects the comments from the destination issue and then adds those comments to the destination issue.

How would you copy the comments from the source issue to the destination issue?

I believe the naming of that is counter-intuitive. It actually takes from the source issue and copies to the new, cloned, issue. It confused me as well, but it does what I want it to. 

Like Gary Spross likes this

Ok, I must have something setup incorrectly then because it's currently not working to copy the comments from the source issue to the new cloned issue.

I've gone through the rule several times and I'm not getting it to work properly.

The rule triggers based on a "clone" link type being established.

Within the rule, the source issue is the issue that was used to do the cloning.

The destination issues is the issue that was cloned.

The Advanced branching is collecting the comments from the destination issue. In this case, that issue would not have any comments (since the clone just occurred and comments aren't copied over, which is the entire point of creating this automation rule).

The rule then adds comments to the issue, "the issue" being the source issue (aka the issue that was used to do the cloning). Since the destination issue (aka the issue that was cloned) has no comments, nothing happens.

Unless I'm completely missing something, I'm not really sure what this rule is doing for you that is solving anything.

I need the rule to copy the comments from the issue that was used to do the cloning to the issue that was cloned. If I could specify which issue to "Add comment" to, that would solve the issue I'm having.

I believe the destination issue in this case is the original issue that was being cloned from because the issue triggering the automation is the cloned issue. 


I just ran through the use case again to check my own sanity and it's working as I understand you're expecting it to. 


Add comment to original issue:


Screenshot 2022-11-17 at 12.33.46 PM.png



Clone issue: 

Screenshot 2022-11-17 at 12.34.58 PM.png


Look at Cloned issue and see the magic: 

Screenshot 2022-11-17 at 12.35.14 PM.png

Like Gary Spross likes this

Thanks for the response Patrick!

The cloning I'm doing is occurring within another automation rule, based on the transition of the issue.

Within the automation rule to copy the comments, the source issue is the original issue (SUP) and the destination issue is the cloned issue (AE).

Screenshot 2022-11-17 154419.jpg

So, that seems to be my problem, because when adding the comment, the logic wants to do it against the source issue. I have no way to tell it to add the comment to the destination issue.

If I could either flip the issue scope of the rule or add the comment to a specific issue, then it would probably work.

Yeah, that is the problem. I just confirmed it by cloning an issue manually. When cloned manually, the source issue is the newly cloned issue and the destination issue is the issue that was cloned from. When cloning occurs from within my automation rule, the subsequent automation rule gets the issues reversed.

I looked into my automation rule that is cloning the issues and I set up the link type backwards... Corrected this and now it's working as expected.

Sorry for so much back and forth, but thank you for going on this journey with me!

Like Patrick Seamars likes this

Awesome! Glad it worked out! Happy to help! 

Like # people like this

As a workaround, you can create a comment that has all of the comments from the triggering issue concatenated.  In the automation, after cloning the issue, create a branch to update all created issues, then add a step to create a comment.

Automation 2022-03-31 074045.jpg

Use the smart-value:   {{triggerIssue.comment.body}}

Automation Step - Add Comment 2022-03-31 074350.jpg

Hi @Patrick Seamars 

thanx for your answer, works perfect when cloning an issue. 
One question, is it possible to genereate this comment with all the previous comments combined but then sorted by date descending? it defaults with an ascending order. 

hope you (or someone else) can help me out! thanx in advance

0 votes

Hello @Tushar.Kamble 


Our app Elements Copy & Sync would let you copy comments (as well as any fields or attachments you want) when you cloning the issue. You can also chose if you want the copied issue to be synchronized with the original.

The Cloud version is not yet available on the Marketplace, but you can sign up to get updates about the release:

Hi @Tushar.Kamble

I don't think so because the comment should be related to the issue. Even if you clone it, you may want to begin another story, sorry.

Otherwise, you can try to export to CSV file your issue and then import it. I am not fan of this method but it works sometimes.

Hope it helps !

Suggest an answer

Log in or Sign up to answer