Roadmap shows Task and Story as Issue without Parent
Asked by Karmandroid Singularity:

This is my first time using JIRA Roadmap with Story - Task relationship.

Actually I am not sure whether it's **Advance Roadmap** or just **Roadmap**. But I created it from this menu:

![Plan Create.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/342718i91285E3ED4FAF00A/image-size/large?v=v2&px=999 "Plan Create.PNG")

Let's say I have below:

*** ** * ** ***

I dont have any Epic, I only have Story and Task

TRN-01 is a Story set with Issue Links "Parent of" :

1. TRN-02 is a Task
2. TRN-03 is a Task

TRN-04 is a standalone Task without any Parent

*** ** * ** ***

When I generate the Roadmap and use hierarchy **Epic to Sub-Task** it shows me "4 Task WIthout Parent" .

Is it normal? Should it have some hierarcy since I set a Parent-Child relation on some of the task?


Answers:
author: Florian Bonniec
body: Hi [@Karmandroid Singularity](/t5/user/viewprofilepage/user-id/3803045)

Your hierarchy is not compatible with Advanced Roadmap. The link type is custom and is not used by Advanced roadmap. Advanced Roadmap use the Parent Link field to reference the parent but you cannot alter the basic JIRA hierarchy which is Epic \> Story/Task?Bug \> Sub-tasks.

With a custom hierarchy like you have you should use another app such as Structure for instance.

Regards

comments: author: Karmandroid Singularity
body: Actually I used the JIRA's default task type.

But turns out task we can't nested Task under Story because they are on the same level. What can be done is to create a Sub-task inside the Story, but then it will be a problem again when a Sub-task should have different Sprint with the Story.

I know it's not common, but imagine a Task/Sub-Task which has a huge amount of works which can't be done in parallel. All of those series of Task/Sub-Task are dependent on each other and we can't remove those dependencies. If we plan a Sprint to follow "This Story must be finished in 1 Sprint" then we will have more than 4 weeks of Sprint only to deliver this Story, where we have other Story which can be deliver within 4 weeks or less.


author: Florian Bonniec
body: For JIRA a Story/Task is considered as completed when all the sub-tasks are completed. Because a Story is supposed to be planned and completed in just one Sprint it means all subtask should be planned in the same sprint it's why they are not displayed in the backlog.

If you need to have a Story across multiple Sprint in order to be completed, that means the Story is to big and should be split.

Regards


author: Karmandroid Singularity
body: Yes, this is kind of trick (or perhaps I overthinking about it).

Let's say the Story is a feature and to finish the feature 5 weeks are needed.

My view about sprint is : in the end of the sprint there must be a version that are ready to deliver and has improvement from the previous version.

In this case when I added the feature as a item to deliver, then the sprint must fit the story size. I can't deliver this features half-way because it is impossible to use.

Well, its possible to deliver like UI/UX visual only, but the functionality is not there yet. But I contemplating whether it will make sense or not.

Anyhow, it's another discussion which not fit to the question :)


Tags: data-center

jira-data-center