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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a user who wants to use the Solution Layer in Jira Align. I think that would be a beneficial feature to turn on as we are a very large organization but am wondering what kinds of things I should consider before doing so.
I assume that it will implement an extra work item layer (along with its objective) that programs would need to link their features to (in other words, they wouldn't be able to link Feature -> Epic anymore but would have to do Feature -> Capability -> Epic). Besides adding that extra work item to the hierarchy are there any other considerations?
Thanks very much!
Lyle- some things to consider before turning on the solution layer:
Once capabilities are enabled, they cannot be turned off
There is NO Solution Room dashboard like the Strategy, Portfolio, Program and Team Room.
Epics created in non-solution portfolio's cannot be moved to portfolios with solution level enabled.
Cannot link Features to Epics if it is from Portfolios with capabilities enabled to Portfolios without capabilities enabled.
Reporting for the solution level is not as robust as program and Portfolio
The capabilities detail panel has limited fields compared to epics and features
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.