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

Change PI and iteration end dates

Would there be anything to consider if we change current PI and iteration (last iteration) end dates?

Thank you.

1 answer

0 votes
Mark Cruth
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 22, 2020

Hi Reddy!

So sorry for not getting you a response sooner. Changing the PI and Sprint Start/End dates may impact how some data displayed in reports, but that's about it. For example, the Scope Change report pivots off of the PI start and end dates, so if you moved either date the report data could change (e.g. if you change the start date to be earlier than originally planned, the report might show a large influx of work after the PI start). 

If you have Jira and Jira Align integrated, here are a few things you need to make sure to do to ensure data syncs up properly:

  • Make sure to update your anchor sprint dates for the PI (not just the PI dates)
  • Make sure you update the sprint dates in Jira, then have your Jira Align admin re-sync each of the boards to update the Sprints in Jira Align to reflect the new dates
  • Double check the sprint mapping in Jira Align to ensure sprints are coming over and mapping properly (Jira and Jira Align expect a consistent cadence to map out future sprints, so if the cadence isn't consistent it's possible that sprints will not map properly)

I hope this helps! 



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events