Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How To: Epic / User Story / SubTask Issue Filtering

Cloudites Owner
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 Leaders.
Oct 21, 2022

This post provides a step by step configuration guide to create a simplified Issue Type structure which enables a Jira project to utilize and report across any number of Epics and their full hierarchy of Linked Child issues.

By default Jira Scrum project templates use Subtasks to create issue associations for Issue Type: Story which unnecessarily complicates reporting and allows non-explicit opportunities for unresolved blocker issues to slip through into a release.


Subtask – Jira secondary Issue Type of Sub-tasks.

Linked Child – User-definable, full feature ITIL4 compliant Jira main Issue Type.


All Epic interconnected issues are using the Jira main Issue Type and can be accessed without traversing across Jira’s main and secondary Issue Type structures.

Linked Child issues have access to the full array of linked issue conditions so non-blockers (linked issue ‘contains’) and blockers (linked issue ‘Cannot finish until linked issue is finished) are clearly articulated.

Epic and/or Story Advanced Search and Dashboard filters can easily be created using a single jql statement.

Does not require the project to rely on Issue Type Hierarchies administration.

How To

Step 1. Navigate to Settings, Issues, Issue Types. Add a new Issue Type. The name is user-definable, I’ve named mine SubTask. Select a preset icon or upload one of your own. I use the Jira default Sub-tasks icon. Save.

Step 2. Navigate to Settings, Issues, Issue Type Schemes. Search for your project and edit the project’s Issue Type Scheme. Add the newly created Issue Type to the list of Available issue types. Save.

Step 3. Navigate to Settings, Issues, Sub-tasks. Disable Sub-tasks. (Yes, you’re reading this correctly! 😄). Confirm.



1. Create Epic main issue
2. Create Story main issue
3. Open Story main issue
4. Populate Epic Link to associate the Story to the Epic
5. Click the Create Linked Issue + icon to create a SubTask
6. Select Issue Type SubTask
7. Select an appropriate Linked Issue condition
8. Fill out all other issue fields as usual


With all Issue Types using the main Jira Issue Type basic and advanced jql filters are usable to report across the full list of Epic issues. This also enables the parentEpic function to be a powerful issue aggregator across Epics.

1 comment

I've never tried this way, but I'll give it a shot. Thx. ☺️


Log in or Sign up to comment