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!


Re-syncing multiple boards/sprints


We moved two product areas to a new product portfolio.  That product portfolio has different program increments.  I've made the necessary changes to the portfolio epics and features pi data and have that cleaned up, but the boards are still mapping to the old program increment anchor sprints. 

I have successfully re-synced future sprints on one of the boards which then mapped them to the new program increment anchor sprints, however, I need to this for about 10 boards. 

I am thinking I could use the Jira Integration tab and choose to "Run Board, Sprint and Fix Version sync along with the search query" but I'm hesitating as to what that query needs to be when all I really want it to resync the sprints.  Can I use this or am I better off to individually resync future sprints on each impacted board?


1 answer

1 accepted

0 votes
Answer accepted
Mark Cruth
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 09, 2021

@Suzanne Matheu - you are correct that you could use the Jira Integration tab and set the "Run Board, Sprint, and Fix Version sync" option and it should do what you're looking to accomplish. I'd recommend making your query focused on just the stories you want to see updated on those boards (you might just do something like "type = story" in addition to a date range). Since the old sprints are in place and locked, the resync won't impact those sprints (which is good if you want the historical data). 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events