You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
It's a long read, but I'm hoping others are trying to leverage their investment in Portfolio, and are willing to engage in this topic.
Modeling plans and resources in Portfolio
Current Understanding / Attempts
Projects When many Projects affect many Products, we would like to know when a specific Project is jeopardizing the release of a given Product. “Release” dependencies in Portfolio are limited to a Project/Board – it does not seem possible to make Projects depend on one another.
Option 1 – Create a cross-functional release across for the Product
Option 2 – Put fixed dates on all projects, if any of them show “Red” - the Product releases they contribute to are in Jeopardy
Option 3 – Task level dependency between Projects ( this is a more generalized implementation of https://community.atlassian.com/t5/Portfolio-for-Jira-questions/How-to-make-portfolio-repect-the-release-order/qaq-p/742666
Staff loading across projects seems to be a missing feature – we’d like know who is over/under-utilized based the hours we enter per project. There appears to be no way to set the global availability of a person, and then determine if the assumed allocation across projects is within the global availability.
Options 1 - create a custom report from the underlying database – what are the options? How do we get insight into the schema?