Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,560,577
Community Members
 
Community Events
185
Community Groups

Portfolio Planning with epic-story-subtask hierarchy

Edited
Lucas Kunneman
Lucas Kunneman Sep 17, 2019

Running JIRA  V7.1.1, with Portfolio V2.2.2. Soon moving to JIRA 8 and portfolio 3.9.

In our project, we've defined several epics with stories. Those stories have a number of sub-tasks, each with effort estimate & assigned to people. Our goal is to get portfolio running to visualize the planning and dependencies (gantt-chart style). I run into the following:

1. Stories are shown in the schedule, but the sub-tasks are not. We need that granularity.  Can that be turned on now? Will it be possible in Portfolio V3.9?
   Note that luckily, the sub-tasks are shown in the 'scope' view. Now to see them in the schedule view!

2. Some subtasks can be done concurrently, while others depend on each other. Does it make sense to use the 'dependency' of issues called 'blocked by'?  This seems intuitive, but Portfolio states a cyclic dependency error when I create such a relation between two subtasks.

Answer
Watch
Like Be the first to like this
490 views

1 answer

0 votes
Deniz Oğuz
Deniz Oğuz
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.
Get recognized
Sep 18, 2019

I don't know the second part. But for the first part, yes you can visualize including subtask:

 

jira-portfolio-hierarchy.png

View More Comments
Lucas Kunneman
Lucas Kunneman Sep 18, 2019

Thanks  Deniz, unfortunately that is 'scope', not schedule.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Portfolio for Jira
Advanced Roadmaps
TAGS
AUG Leaders

Atlassian Community Events

See all events