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
Next: Root
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.
We have Jira Align and Jira Cloud integration.
As a part of reorganization, we need to move few programs from one Solution to another Solution in the same Portfolio in Jira Align.
Is there any implication? Are there any best practices / recommendations here? Please suggest
My friend @Peter Jessen wrote a great article about the implications of moving a Team here: https://community.atlassian.com/t5/Jira-Align-questions/What-are-the-implications-of-moving-a-team-from-1-train-to/qaq-p/1339252
A lot of the points he raised in that article about a team also apply to an entire Program.
There are many good reasons to restructure the portfolios, solutions and programs, especially as you discover more about how your teams work together to deliver value to your customers. (There are bad reasons too! Constantly reshuffling teams makes it difficult to build any sort of momentum, team cohesiveness, and predictability.)
A couple key considerations:
In general, the best practice is
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.