Why does setting Start Date for a Release change the predicted Completion Date?

I'm using the Version Report to forecast a predicted completion date and I'm not very confident in what I'm seeing so far.  I noticed that changing the Release Start date changes the predicted completion date even if the total amount of work remains the same. I also notice that the Completed Story Points value is unchanged when I adjust the Start date.

My reason for setting the Start date earlier is that it reflects when work actually began.  However, I don't see Completed Story Points for that work even though the items in question are showing up in the set of Completed Issues shown further down in the Version Report.  My concern is that the calculated velocity seems like it's including a large period of zero velocity and this reduces the overall velocity rate to predict a much later release date.  If I leave the Start date empty (it's optional), The predicted release date is much sooner.  Considering the high-stakes nature of reporting a predicted release date, I really need to understand how this works. :-)


1 answer

I guess the linear regression then is done only from start date.

How do you change the start date?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

90 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you