nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Clone Child Issues tickbox not displaying

James Walters_69hv0o

Hi there, having a new issue that's only just cropped up.

We have a template story with subtasks that we clone to ensure we follow the procedures laid out for each project.

However, today, when we went to clone an issue, the 'clone child issues' tickbox did not display. Upon cloning the story, the child issues did not appear.

We refreshed the page, to no effect, and logged out then back in again. Nada.

I have a personal Jira board I use for freelancing, and that still has the 'clone child issues' tickbox.

Any thoughts on how we can fix this?

Jira no child issue tickbox.png

Accepted answers

All comments

John Funk

Hi James - Welcome to the Atlassian Community!

Is this a Team-managed or Company-managed project? Was it working on this same project before? Or just the same Jira site and a different project?

James Walters_69hv0o

Thank you

Team managed, on the free version. It worked on this project up until today for the last 16 months on this project, this is a brand new issue that's just only cropped.

It still works on a different personal board of mine that I use personally.

I just created a second test project, and it also doesn't have the cloning child issues option.

Jira no child issue tickbox 2.png

Could this be related to the new navigation shift?

I created a new project on my personal board, and it does have the clone child issues, so I'm really confused as to why it's not working on my work board...

Jira no child issue tickbox 3.png

John Funk

Can you check an existing Company-managed project to see if it is available on that one?

James Walters_69hv0o

I run my board separate to the company one, as they work on an older/more basic version of Jira (Data Centre). So mine is only available to 4 of my team members. It's a completely separate entity.

Bill Sheboy

Hi @James Walters

It appears that symptom was just logged today as a defect in the public backlog. Please watch / vote for it to see any progress:

https://jira.atlassian.com/browse/JRACLOUD-93055

Kind regards,
Bill

John Funk

Had a feeling as such - that was what I was trying to get to, to see if a bug needed to be entered. :-)

James Walters_69hv0o

Thanks Bill, and thanks John for sticking with me there

Clara Belin-Brosseau_Elevatic

Hello @James Walters

As an alternative to Jira native cloning feature that can be sometimes quite limited, I can suggest trying our app Elements Copy & Sync. It allows you to perform cloning of a full hierarchy of issues, meaning with all the child issues at once.

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).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-issue

jira-clone