nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the best way to manage this scenario ? -important help required

Preem Prakassh Dayaal

Hi Experts

I really need some urgent help around this ...

My problem statement is as below

I have a book of work which has 5 tracks and each track has some key items to be completed before you can say that the track is completed

for example

Book of Work

Track 1 - items 1.a , items 1.b etc

Track 2 - items 2.a , items 2.b etc

Now the complication comes is when each track needs to be managed at the micro level as well. For example

Track 1 - item 1.a has got 10 stories which on a daily basis needs to be tracked and assessed. So in essence , a track may have 2 items however they may have 10 stories to be completed .

What is the most effective way to deal with this scenario on Jira ?

How can this be managed so that while people can manage stories and at the same time, senior management can get a view at the track - items wise on daily basis as well..

Any immediate suggestions shall help

Regards

Preem

Accepted answers

Julie d_Antin _Elements__bsgnak

Hi @Preem Prakassh Dayaal

Sounds like you would be a good candidate for Advanced Roadmaps since it allows you to create issues above the Epic and better communicate the big picture for stakeholders, all while letting users keep working on individual Jira issues (whether they be Stories, Tasks, Bugs...)

A good place to start is just with this: https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps

There's also a YouTube playlist https://www.youtube.com/playlist?list=PLLKGNJ358oRl_FRuG6wIcc8PrDqVf488K

I'll let other Community members chime in with any other tips or recommendations.

All comments

Julie d_Antin _Elements__bsgnak

Hi @Preem Prakassh Dayaal

A good place to start is just with this: https://www.atlassian.com/software/jira/guides/roadmaps/advanced-roadmaps

There's also a YouTube playlist https://www.youtube.com/playlist?list=PLLKGNJ358oRl_FRuG6wIcc8PrDqVf488K

I'll let other Community members chime in with any other tips or recommendations.

Preem Prakassh Dayaal

Thanks Laura .

Kathryn Vargas _Tempo_

Hi @Preem Prakassh Dayaal,

To add to what @Julie d_Antin _Elements_ mentioned, it sounds like you would need to add a few levels above the Epic. Advanced Roadmaps allows this, but there are also a number of third-apps in the Atlassian Marketplace that could help you build this issue hierarchy, while giving you more flexibility to work with the the higher and lower levels. Structure for Jira is one of them.

Structure lets you visualize default parent-child relationships in Jira (like epic > story > sub-task), but its real power is in its ability and flexibility to visualize any other issue links between stories, tasks, and other issue types in an organization – in a spreadsheet-like view.

For example, here's Structure in action with a 5-level hierarchy:

The rules or "generators" up top define the issues and the issue hierarchy you see, so you could easily create a view for management that doesn't include subtasks, for example.

What's handy too is you can add add any Jira field as a column, so that you can gather all the relevant information in one place. From here, you can sum up values in any column that contains numeric values (like Story Points and Estimates) which is useful for reporting, sprint planning, planning, etc.

Disclaimer: I'm part of the Structure team, but I hope this helps!

Best,
Kathryn

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud