Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


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!


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
Community Members
Community Events
Community Groups

What are the implications of moving a Program from one Solution to another Solution in Jira Align?

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

1 answer

1 accepted

4 votes
Answer accepted
Rich Sparks
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 10, 2022 • edited

My friend @Peter Jessen wrote a great article about the implications of moving a Team here:

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:

  • Try to make changes on PI boundaries. That way, you can keep and learn from any metrics you gathered in previous PIs.
  • Take the opportunity to clean up your Jira backlogs. In many cases, it is best to create new Jira projects and boards for the teams that are moving and only move the relevant Jira issues into the new projects.

In general, the best practice is 

  1. Set up the new program in Jira Align (and we recommend a new project in Jira
  2. Set up each of the teams in the new program
  3. Set up the teams' backlog in Jira (move only the necessary issues to the new project)
  4. Update the Jira project and board mapping in Jira Align with the new programs
  5. When you're all set and things are working as you wish, deactivate the old teams and programs in Jira Align (so they don't show in drop-down lists).
  6. If you added new Jira projects and aren't using the old ones any more, remove them from the Jira Align project list so the connector doesn't keep checking.

Thanks @Rich Sparks for a prompt response!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events