Reports effected by iterations outside the team areas associated timeline.
Hi Guys,
I have multiple timelines set in my project.
Each timeline is associated with a Team Area and has a child iteration.
I have the iteration in each timeline set to "current iteration".
Each of the iterations have different start dates.
e.g
Team A Timeline
-- Team A Iteration - start date 1st january
Team B Timeline
-- Team B Iteration - start date 11th january
Team C Timeline
-- Team C Iteration - start date 21st january
When I load up the Team Area dashboard I have noticed the start date of some reports is skewed by iterations outside the teams scope.
So using the example above if I load the dashboard for Team B.
Start date of the iteration is 11th january but reports like burndown/burnup show start date as the 1st January.
It seems to be taking the earliest start date from any active iteration within the project and using this in the reports.
But the team is associated with its own timeline so why would it be using the dates from iterations outside its timelines scope?
|
Be the first one to answer this question!
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.