How to Add a Parent Link in Jira

Most teams don’t lose deals or miss deadlines because they lack talent. They lose them because their work tracking is a mess — issues floating without context, no one knowing what depends on what, and every standup turning into a detective session.

Adding a parent link in Jira is one of the simplest fixes. It connects child issues to their parent, creates a clear hierarchy, and gives everyone instant visibility into what work belongs where.

This guide shows you exactly how to do it — whether you’re on a company-managed or team-managed project.

What Is a Parent Link in Jira?

A parent link in Jira is a relationship that connects a lower-level issue (like a subtask or story) to a higher-level issue (like an epic or initiative). It tells Jira — and your team — where this piece of work sits in the bigger picture.

According to Atlassian, over 65,000 companies use Jira to manage their work. Yet one of the most common friction points reported by teams is poor issue hierarchy visibility. Parent links directly solve that.

The hierarchy in Jira company-managed projects typically looks like this:

• Epic → contains Stories, Tasks, Bugs
• Story / Task / Bug → contains Subtasks
• Initiative (in Jira Premium) → contains Epics

When a parent link is missing, issues become orphaned. They show up in backlogs without context, slow down sprint planning, and make progress reports nearly impossible to trust.

Why Parent Links Matter More Than You Think

Here’s a stat worth sitting with: teams that use structured issue hierarchies in Jira report up to 35% faster sprint planning because everyone already understands the scope before the meeting starts.

Parent links aren’t just organizational hygiene. They directly impact:

• Roadmap accuracy — parent links power the Jira roadmap view, so missing links = a broken roadmap
• Velocity tracking — story points roll up correctly only when hierarchy is set
• Reporting — dashboards and burn-down charts depend on proper issue relationships
• Cross-team alignment — when multiple teams work on the same product, parent links show who owns what

A 2023 survey by Project Management Institute found that poor project visibility is cited by 44% of project failures — and Jira hierarchy issues are a major contributor for software teams.

Types of Issue Links in Jira

Before adding a parent link, it helps to know the difference between the two main relationship types:

Parent Link — A structural hierarchy relationship. It tells Jira that this issue belongs to a parent issue (e.g., a Story belongs to an Epic).

Issue Link — A contextual relationship. It tells Jira how issues relate to each other (e.g., “blocks,” “is blocked by,” “relates to,” “duplicates”).

Parent links are built into Jira’s hierarchy model. Issue links are manually defined relationships between any two issues regardless of type.

How to Add a Parent Link in Jira (Company-Managed Projects)

Company-managed projects are the most common setup for larger teams. Here’s the exact process:

Step 1 — Open the child issue
Navigate to the issue you want to assign a parent to. This is typically a Story, Task, Bug, or Subtask.

Step 2 — Find the “Parent” field
In the issue detail view, look at the right-hand panel (or the top of the form in older layouts). You’ll see a field labeled “Parent” or “Epic Link” depending on your Jira version and project configuration.

• In Next-gen / team-managed projects, this field shows as “Parent”
• In classic company-managed projects, Stories link to Epics via the “Epic Link” field
• Subtasks use the “Parent” field automatically

Step 3 — Click the Parent field
A dropdown or search box appears. Start typing the name or issue key of the parent issue (e.g., “PROJ-42” or “User Authentication Epic”).

Step 4 — Select the parent issue
Click on the correct parent from the search results. Jira saves the relationship automatically.

Step 5 — Confirm the link
Refresh the issue or check the breadcrumb at the top of the page. The parent should now appear as a clickable link.

How to Add a Parent Link in Jira (Team-Managed Projects)

Team-managed projects (formerly “next-gen”) have a slightly different interface but the same logic.

Step 1 — Open the issue
Click on the issue you want to nest under a parent.

Step 2 — Look for the “Parent” field in the issue view
In team-managed projects, the Parent field is prominently shown near the top of the issue detail panel.

Step 3 — Click on the Parent field
If no parent is set, it shows as “None.” Click it to open the search.

Step 4 — Search and select
Type the parent issue name or key. Select it from the dropdown.

Step 5 — Save
The link is saved instantly. The issue now shows in the parent’s child list.

How to Add a Parent Link in Jira Using the Backlog View

The backlog gives you a faster way to set or change parent links in bulk — especially useful during sprint planning.

Step 1 — Open the Backlog
Go to your project and click “Backlog” in the left sidebar.

Step 2 — Right-click an issue
In company-managed projects, right-clicking an issue in the backlog opens a context menu with relationship options.

Step 3 — Select “Set Parent”
Click this option and choose the parent issue from the panel that appears.

Step 4 — Confirm
The issue is now nested under the selected parent directly in the backlog view.

How to Add a Parent Link via the Roadmap View

If you’re using Jira’s roadmap feature, you can assign parents visually.

Step 1 — Open Roadmap
Navigate to your project and click “Roadmap” in the left sidebar. This view is available on company-managed projects with roadmap enabled, and on all team-managed projects.

Step 2 — Drag and drop issues under an Epic
In the roadmap, issues that aren’t assigned to an Epic appear in a separate section. You can drag them directly under the correct Epic row to set the parent relationship.

Step 3 — Click to assign
Alternatively, click on an unassigned issue in the roadmap. The issue detail panel opens on the right. Set the parent from there.

How to Change or Remove a Parent Link in Jira

Changing a parent is as simple as adding one.

To change the parent:
Open the issue, click the current parent name in the Parent field, clear it, and search for the new parent. Select it and save.

To remove the parent (for company-managed projects):
Open the issue and click the “X” next to the parent link in the field. Note that subtasks cannot have their parent removed — they must be converted to a different issue type first.

To remove the parent (for team-managed projects):
Click the Parent field, then select the “None” option or clear the field.

How to Bulk Add Parent Links in Jira

For large migrations or restructuring sprints, bulk editing saves hours.

Using Jira’s Bulk Edit feature:

Step 1 — Go to the issue list or backlog
In the backlog or issue navigator, select multiple issues using the checkbox on the left side of each issue.

Step 2 — Click “Bulk Change” or “Edit”
Depending on your Jira version, look for the bulk action button at the top of the selected list.

Step 3 — Choose “Edit Issues”
Select “Edit Issues” from the bulk change options.

Step 4 — Set the Epic Link or Parent field
In the bulk edit form, find the Epic Link (for Stories) or Parent field (for Subtasks). Enter the target parent issue.

Step 5 — Apply changes
Confirm and apply. All selected issues will be linked to the same parent.

Note: Jira’s bulk edit for Epic Link is available in company-managed projects. For team-managed projects, you may need to update issues individually or use the Jira API for bulk parent assignments.

Common Errors When Adding Parent Links in Jira

Even with the right steps, a few things can go wrong. Here’s what to watch for:

“Parent field not visible”
The field might be hidden from the screen layout. Go to Project Settings → Issue Types → [Issue Type] → Fields and ensure the Parent or Epic Link field is added to the screen.

“Can’t link a Story to another Story as parent”
Jira’s hierarchy rules apply strictly. A Story cannot be the parent of another Story unless you’re using custom hierarchies in Jira Premium (with Advanced Roadmaps). Stories can only link to Epics as parents.

“Epic Link is greyed out”
This usually means the Epic you’re trying to link to is in a different project and cross-project Epic linking is not enabled. Check your project configuration or move the Epic to the same project.

“Parent link doesn’t show on roadmap”
The roadmap only shows parent links between issues within the supported hierarchy. If the parent issue type isn’t recognized by the roadmap (e.g., a custom type without hierarchy mapping), the link won’t appear visually.

How to Add a Parent Link Using the Jira API

For teams managing Jira programmatically or at scale, the REST API gives full control.

Endpoint:

PUT /rest/api/3/issue/{issueIdOrKey}

Request body (setting a parent):

{

  “fields”: {

    “parent”: {

      “key”: “PROJ-42”

    }

  }

}

For Epic Link (classic projects):

{

  “fields”: {

    “customfield_10014”: “PROJ-42”

  }

}

Replace customfield_10014 with your actual Epic Link field ID — this varies by instance. You can find it via /rest/api/3/field.

According to Atlassian’s developer documentation, over 1 million API calls per day are made to Jira REST endpoints by integration tools and automation scripts — showing just how central programmatic management has become.

Best Practices for Managing Parent Links in Jira

Teams that get the most value from Jira’s hierarchy follow a few consistent habits:

Set parent links at issue creation — Don’t wait until sprint planning. Assign the parent when the issue is created so it lands in the right Epic from day one.

Audit orphaned issues weekly — Use Jira’s issue navigator with a filter like issueType = Story AND “Epic Link” is EMPTY to find and fix unlinked issues before they cause roadmap gaps.

Use consistent naming conventions for Epics — When team members search for parent issues, clear Epic names like “Q2 Checkout Redesign” surface faster than vague names like “Frontend Work.”

Leverage the roadmap as a living document — After setting parent links, review the roadmap in weekly team syncs. It makes dependencies obvious and keeps everyone honest about scope.

Educate new team members early — Research shows that 58% of project inefficiencies traced back to Jira stem from improper setup and training during onboarding, not tool limitations.

Conclusion

Adding a parent link in Jira takes under a minute — but getting into the habit of doing it consistently transforms how your team tracks work. Issues stop floating. Roadmaps start making sense. Sprint planning stops being a guessing game.

The setup is straightforward: open the child issue, find the Parent or Epic Link field, search for and select the parent, and save. Whether you’re doing it one issue at a time, in bulk, or through the API, the hierarchy you create feeds directly into every report, roadmap, and sprint review your team runs.

The teams with the clearest Jira hierarchy are usually the same teams with the clearest pipeline. Both come from the same discipline: knowing exactly where every piece of work sits, who it belongs to, and what it’s moving toward.

If you want that same clarity in your outbound pipeline — with targeting, campaign design, and a scaling system that runs consistently — SalesSo builds it for you. Book a strategy meeting and let’s map out what your outbound engine should look like.