Hi Justin, sprints are indeed expected with the start date of the first release configured in the releases tab. If there are multiple release streams, the earlierst release across all streams is taken for the start of the first sprint. It should not be necessary to set any start dates on the items themselves.
That said, there might be another root cause why it behaves differently.
Have you done a plan update as part of trying the product? You could see that if you look at the first label in the timeline: Does it say "23/3 - Start" or "23/3 - Update" ? An update is normally used to keep the plan updated regularly, and "plan forward" from a given point in time, thus the start date is moved forward as well to what you set in the update from date dialog. If this is the case, you can "reset" the plan update date by choosing "Plan > Update from date", and select a date prior to March 16 - always the later date of the release and plan udpate is taken.
If you can't make sense of it still, feel free to send along/attach an anonymous plan export (Plan > Export > Render data anonymous) so we can take a quick look.
Cheers, Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.