"Parent link not retained when using 'Create another' during issue creation"

[Diallo]

Hello, I'm asking this question just to understand the correct way to link child issues to their parent (project, features, epics). I have a problem with the parent link on issues. I wanted to create multiple issues at the same time using the "Create another" option during issue creation, but when I set a parent link, it only applies to the first issue. For the following ones, no parent link is set.

Has anyone else experienced this? If so, how did you handle it? It makes it really impossible to do it efficiently.

[Paul Glantschnig _Appfire_]

Hi @Diallo, 

Jan and Marc are right that the Parent field doesn't carry over by default. I believe it's intentional to avoid accidental mass-linking. There is one native tweak that could help though: when you open the "Create issue" dialog, go to More actions (…) > Configure Fields and add the Parent field to the screen.

Once it's visible in the form, Jira should pre-populate it when you use "Create another", since it remembers field values from the previous issue. Worth trying if you haven't already.

If you need to set the parent on a larger batch of already-created issues, dragging them onto the parent in the timeline or list view works for smaller sets.

If you're open to a Marketplace app, JXL for Jira makes this significantly easier for larger batches in two ways:

1. Bulk parent reassignment — select multiple issues in JXL and update the Parent field for all of them in one step, no one-by-one clicking.

2. Create from hierarchy context — in JXL's hierarchy view, you can create new child issues directly under a parent row. The parent link is set automatically since you're in that context, so you don't need to re-select the parent for each issue.

The gif above, showcases bulk changing the parent for multiple child issues at once in JXL.

Cheers, Paul

Disclosure: I work for the team that builds JXL.

[Diallo]

@Paul Glantschnig _Appfire_ , thank you for you feedback,

Yes but, the parent field only concerns epics, tasks, stories, bugs and subtasks (using Jira's native parent field). For issue types above epic level, they are linked to each other via Linked Work Items (the superior is the parent, the inferior is "Child of")

[Marc -Devoteam-]

Hi @Diallo 

@Jan is mostly right here.

The Parent field is never carried over on creating a new issue, the same as for the link issue field.

This is as intended, as this could be forgotten and then all new work items would be linked or child of an issue

[Diallo]

@Marc -Devoteam- , thank you for feedback, 

It works great for tasks, bugs, stories and subtasks — I use the native Jira parent field to link them to their parent. For issue types above epic level, they are linked via Linked Work Items ("Child of")

[Jan]

Yes that’s expected behavior in Jira.

The “Create another” option does not reliably carry over the Parent field (especially for Epic/Parent Link fields). It often resets after the first issue.

Quick ways to handle it:

• Use Bulk Create (CSV import) best for many issues with same parent
• Create issues first then bulk edit → set parent
• Use issue templates / automation (if recurring)

Short answer:

You’re not doing anything wrong — it’s a Jira limitation. Use bulk edit or backlog drag & drop for efficiency.

[Diallo]

@Jan ,  thank you for you feedback,

I am going to do a 5-minute automation that will put the epics in my features. it’s annoying for the long term, 

it works well when I create multiple bug tasks, or under tasks I create as much as I want. he puts it well in their parent, => but at the moment I am using Parent the native jira field.