it looks like rtc remembers our release date even though we changed it.
A few months ago, our release end date was changed. At that time, we went into timelines and edited the end date to reflect the new ship date of the release. Today, we were running end of sprint reports and the release burn down chart now has a line that was not there last sprint; the line is labeled 'release date'. Also the ideal line hits 0 on the chart this month. This month was the original date for the end of the release. It looks like RTC is remembering our original release end date. We thought we had changed all the spots where the end date of the release was recorded, but perhaps we have missed one. We edited the project area and edited the release in the timeline section, but that all looks right. Do you have any other suggestions?
Thank you. charles. |
One answer
|
Well, we figured this one out. It appears that the release current iteration was what was remembering the old date. We selected the "release" iteration, which had the blue triangle by it, and noticed that the icon that says 'Set the Selected Iteration as Current' was available. When we clicked it and tried again, our problem was solved.
So, the next time we have to change the release end date, we need to remember to 'Set the Selected Iteration as Current' AFTER changing the date so we will avoid this problem in the future. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.