​@Happytoon - We do not actively use Strategy but from my experience when working with it in a sandbox I found this to be a large gap in the functionality.  There is an enhancement request to include strategic hierarchy levels when building a portfolio.  You may want to vote on it to help push it up the priority list: https://e1.spigit.com/e1prmcontinuous/Page/ViewIdea?ideaid=8267

Best regards,

Pam

NASCO

Hi,

We currently CAN filter Work Portfolios by Strategic Hierarchy (we don’t use Outcomes). I can’t recall if this attribute was created for us by a Planview consultant or not. But this allows us to choose any node on the Strategic Hierarchy and the portfolio will only include those projects that are associated with it. This feature was essential to the roll-out the Strategy functionality.

Hi ​@Happytoon, There are two columns you can add to your work portfolio column set: Strategies and Outcomes. However, they may not be ideal if your work is associated to multiple strategies, as the strategy and outcome entities are separated by semicolons, and these attributes can't be used in your portfolio definition. What ​@SilFurman suggested is the best option and it’s available if you your strategic module is enabled. 

 

Hi All, 
Thanks for your replies above…
The “Strategy Hierarchy” doesn’t work in my case as we have a hierarchy of :
Strategy A
|___ Outcome A1
|        |___ Project A1.1
|        |___ Project A1.2
|___ Outcome A2
|        |___ Project A2.1
...
Using the Strategy Hierarchy in a portfolio definition only shows the projects directly associated to the Strategy (in the case above, none).
I don’t have “outcome” column in the work portfolio definition.

As a work around, I completely reorganise my work structure and recreated the “strategy → outcome → project” hierarchy in the work primary structure… (not ideal but it works for now)

Thanks all.

Tony