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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,558,456
Community Members
 
Community Events
184
Community Groups

Will moving a sprint board to a different project preserve sprint history?

I know you can move a board from one project to another. If it's a sprint board, will the history, like velocity, be preserved in that move?

I tried this in our sandbox and the velocity graph has commitment history but not completed history. I also moved the issues to the new project. I believe I moved the issues first and then the board. 

1 answer

1 accepted

0 votes
Answer accepted
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 08, 2023

Hi @Maroline Johnson

I am not really sure what you mean with moving a board to a different project. If you mean changing the board location, I would expect that should not impact any historical data. But as you also say you are moving issues from one project to another, that inevitably will have a lot more impact.

A board is essentially just a view on a set of issues in Jira. Which issues are displayed on the board is determined by the board filter, which you can find under Board settings > General. When you start moving issues between projects and they are no longer part of the board filter's results, you are bound to see impact on the data in your reports.

Hope this helps!

Hello @Walter Buggenhout _ACA IT_ 

Thank you very much for your response! Your call out regarding the board filter ended up being the issue. It was filtering issues down to the previous project, and as soon as I updated that, the Velocity report was showing as expected. 

Thanks again for your help! 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events