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

Jira Plans not showing the Sub-tasks created within the Initiative

I have a jira plan created having Hierarchy View listing from Initiative to Subtasks. Subtasks created within the Initiative Issue Type are not displaying in the Plans/Roadmap View. All Input Sources and Filters conditions are configured correctly but no luck in displaying the subtasks.

2 answers

I was having the same issue, but mine was filter related Screenshot 2023-01-30 133543.png

0 votes

@Sivakumar Vasagar -

Welcome to the community.  Can you check to ensure that your plan's configuration didn't exclude the subtask as defined in the Exclusion Rules (via Plan's configuration the "..." symbol)?

I do have a case where I ended up and recreated the plan again, then issues are showing up properly.  However, my previous plan failed to display properly.

I would also recommend you to submit a formal support request with Atlassian Support ( for additional assistance.

Please let me know of what Atlassian Support team has to say about this issue.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

@Joseph Chung Yin thanks for your response. I do not have any conditions configured in the Exclusion Rules. Also i recreated the plan again with no exclusion conditions, still the sub tasks created within the Initiative Issue type does not show up in the Plan View.

@Sivakumar Vasagar -

Just found something interesting that the subtasks seem to show up only if one is viewing the "Basic View".


I would recommend you to reach out to Atlassian support for additional assistance.  Please post back their response to your ask.

Best, Joseph

@Joseph Chung Yin - The view i have been accessing the plan is the Basic View. But the difference in my case is that the subtasks are created directly under the initiative Issue type as compared to your case of having the subtasks created under the Story Issue Type.

@Sivakumar Vasagar -

Here is another observation with Advanced Roadmap for Jira regarding to Initiative issue type.  You should confirm it with Atlassian Support team to see if my observation is correct.

Observation -

Initiative is a parent of Epic issue type and it allows you to create subtask under it in the UI.  However, the AR for Jira Issue Hierarchy configuration doesn't support subtask roll-up directly against the Initiative.  Therefore, the plan will not display subtasks associated with the Initiative issue.  Another question to you is that why you want to create subtask against Initiative issue type?  Again, Epic issues roll up to Initiative issues, thus the usage of subtasks seem to be incorrect.


NOTE - If you are using Jira Server/Data Center env, the subtasks associated to an Initiative shows up properly but not in the Cloud env.  Don't know if there is a bug within the Cloud env or it is by design.

Hope this further assist your question.  As mentioned above, please confirm with Atlassian Support and post their replies to share with us in the community.

Best, Joseph

None of the information was helpful. This sub-task probem has been going on for years and I wonder why it hasn't been solved so far. Or at least supply some discription on how to tackle the issue.

It's not a "problem" to most. 

Sub-tasks are entirely a fragment of their parent issue, and are pretty much useless when added to issues above the level of Epic (and, for most Epics to be honest).  Most people simply don't add sub-tasks to initiatives or epics.

Like Joseph Chung Yin likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events