Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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
4,552,549
Community Members
 
Community Events
184
Community Groups

How to track cross-portfolio dependencies?

Two product owners develop two different epics A and B (two different projects/scrum boards) and work on two different portfolio plans.

As a first PO i don't want to plan epic B (because this functionality develops second PO and different Dev Team) but i need to know that my epic A is blocked by epic B and need to know when it will be resolved.

When i set "is blocked by" relation between that two epics in Jira, i don't see that relation in portfolio and portfolio ignores that situation in planning.
I don't want to import all other boards (just in case) to monitor cross-portfolio dependencies between "two issues". Is it possible? Any suggestions?

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 12, 2018

Hello,

Currently Portfolio only tracks Dependencies in a single plan.

We have the Following feature request tracking interest in this, make sure to add your vote to help bump up the priority on the feature:

Manually associating a Earliest Start date that likes up with the expected completion date of the other issue in the alternate plan would be the best way to address this for the moment.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events