Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Automation - Unable to copy existing comments when cloning an issue via automation on status change

Automation - Unable to copy existing comments when cloning an issue via automation on status change

Cody Ouimet
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 30, 2025

As the title suggests, I'm setting up some automation for cloning a issue from one project to another on a status transition. This isn't too dissimilar from the normal JSM workflows where you would copy a JSM issue into a regular Jira project for a dev to work on, but without the JSM. I've got it copy comments from either issue to the other when a comment is added post-cloning and issue linking, but I for the life of me cannot get pre-existing comments to copy over to the cloned issue.

 

I've tried following this guide: https://confluence.atlassian.com/jirakb/how-to-copy-comments-from-the-original-issue-to-the-cloned-issue-1236601599.html which is what I got to work essentially for copying new comments, but I can't seem to get it to work on existing. I did have a small breakthrough recently where I got it to copy comments from the OG issue onto the OG issue again, but still no luck on my actual goal.

2 answers

0 votes
Clara Belin-Brosseau_Elements
Atlassian Partner
November 3, 2025

Hi @Cody Ouimet

If Jira Automation can’t copy existing comments when cloning an issue, you can achieve this easily with our app Elements Copy & Sync which is dedicated to cloning and synchronization of Jira issues.

Unlike native automation, Elements Copy & Sync lets you clone issues across projects and copy all comments (existing and future) in one go, without needing complex scripting or workarounds.

Here’s how to set it up:

  1. Create a recipe

    1. In your Jira project settings, go to Elements Copy & Sync.

    2. Create a new Recipe (this defines what data to copy or sync between issues).

  2. Define the target project and issue type

    1. Set the Recipe to clone the issue to the destination project (here, from a JSM to a Jira project).

    2. Choose the issue type.

  3. Include comments in the copy options

    1. Under Copy Options, enable Comments so that all existing comments from the source issue are copied during the clone.

    2. You can also decide whether to include attachments, links, or field values.

Capture d’écran 2025-11-03 à 10.54.55.png4. Enable synchronization (Optional)

  1. If you also want future comments to sync between the two issues, enable the Sync option in the Recipe.

  2. This ensures that whenever someone adds a new comment in one issue, it automatically appears in the linked issue.

5. Trigger the recipe

  1. You can trigger the recipe via a post-function meaning the comments cloning while happen during a status change.

Don't hesitate to try the configuration, the app is for free for 30 days.

I hope this helped :) 

0 votes
Mohanraj Thangamuthu
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2025

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events