The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

When I clone a story the child issues are not being cloned

Ron Metzler
March 17, 2025

I deleted an automation rule that wasn;t working as expected but now when I clone a story the child issues are not being cloned

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Clara Belin-Brosseau_Elements
Atlassian Partner
March 26, 2025

Hi @Ron Metzler

If you're seeking for an easier way to clone a parent issue and all associated child issues, you can try our app Elements Copy & Sync that allows you to clone and sync issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

Elements Copy & Sync - Copy full hierarchy of issues .png

You can have a look at the documentation here.

Don't hesitate to try the app, it's free during 30 days and stays free under 10 users.

0 votes
Laurie Sciutti
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 17, 2025

Hey @Ron Metzler ~ was the automation rule that you deleted the one that auto-generated the child issues?  Need a little more info here to assist....

Ron Metzler
March 17, 2025

No, it was a new automation rule that I created to keep the child issue status the same with the cloned story.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events