Tips for Tracking Linked Issues in Jira Projects

[Babar Brohi]

Hi everyone! I’m trying to improve how we track linked issues in our Jira projects. For example, if I have a parent Epic and several Tasks linked to it, I’d like to automatically display each child’s status and assigned user in a summary table for easy reporting.

Has anyone implemented a clean solution for this? I came across a helpful guide that explains using Jira Automation to summarize linked issues: reference link

Would love to hear how others handle linked issue reporting and dashboard summaries in their Jira projects.

[Martin Runge]

Hi @Babar Brohi

Welcome to the Atlassian community.

This is a common challenge. Being able to see the real-time status of linked issues without opening each one is important for project visibility. Based on your comfort with different tools and what you need, here are four ways I like to approach this:

• I usually rely on the built-in Epic "Child Issues" panel. Most of the time, we use Plans to view blocked and other linked work items, along with their statuses.
• Sometimes, I set up Jira Automation to summarize linked issues in a specific field.
• We also built a custom Forge app to show real-time status for certain custom fields or asset information for one customer.
• Some teams prefer to use dashboards to view and report on all blocking issues, for example, in a list view. They prioritize these issues to keep their workflow moving smoothly.

[Daryl Marsh]

I'm going to assume by your description that you are using a parent/child relationship and not actually linked issues. What has helped us is using an automation to sync the child status' with the parent. So, for example, when a child task is transitioned to 'In Progress' the parent task is also moved to an 'In Progress' status. And when all child tasks have been closed, the parent closes as well. There are some drawbacks to this configuration but it works.

This has helped with reporting, as most folks don't need to be in the weeds at the story/task level, but still want to know progress is being made. Also using Jira Plans can help as well because it displays progress bars on the parent.

[Paul Glantschnig [Appfire]]

Hi @Babar Brohi , welcome to the community!

JQL dashboards, Automation, and Plans are great suggestions and all solid approaches depending on your setup.

Just to add another option, if you are open to marketplace solutions: my team and I work on JXL for Jira, which can also handle this.

You'd create a sheet scoped to your project, enable the hierarchy, and you'd see your Epics with all children nested underneath — status, assignee, and whatever other columns you need, all in one view.

It also rolls up things like status distribution or done percentage at the Epic level, which is handy for the kind of reporting you're describing.

Might be worth a look if the native approaches don't quite get you there.

Disclosure: I work for the team that builds JXL.

Best regards, Paul

[Himanshu Tiwary]

Hi @Babar Brohi ,

Thanks for raising this interesting question. Tracking child issue details under an Epic is a common reporting need, and there are a few approaches that might help.

Here are a couple of suggestions you could consider:

• Using JQL + Dashboard Gadgets

You can create a filter with JQL such as:

Epic Link = EPIC-KEY

Then use dashboard gadgets like Filter Results or Two-Dimensional Filter Statistics to display status, assignee, and other fields for all issues under the Epic.

• Using Jira Automation

You could create an automation rule and use the Lookup Issues action with a query like:

Epic Link = {{issue.key}}

This can help generate a summarized view of child issues (status, assignee, etc.) in a comment or custom field.

• Epic Panel / Roadmap View

If the goal is quick visibility rather than reporting, the Epic panel or roadmap view can also give a clear overview of child issue progress.

Hope this helps, and it would be great to hear what approach works best for your use case.

[Arkadiusz Wroblewski]

Hello and welcome @Babar Brohi 

Your post don't make sense. Link even less.

Epic with Tasks/Stories under it is not even really a linked issues use case, but a parent/child hierarchy...