It's all about the answers!

Ask a question

Advanced Release Burndown chart ignores stories assigned to the correct timeline

Denilson Nastacio (2122) | asked Mar 25 '13, 7:05 p.m.
I have an RTC share with multiple timelines, let's call it "current" and "new" . "current" is the project timeline.
I have a team called "T.current" assigned to the timeline "current"  and another team ""  assigned to the timeline "new".

In the "Work Item Categories" for the project, I have:
<any timeline> :  team "T.current" associated with category "Development"
"current" timeline : same as <any timeline>, that is team "T.current" associated with category "Development"
"new" timeline: team "" associated with category "Development". In other words, the same category is assigned to different teams in different timelines.

When I plot the Advanced Burndown chart, I pick "new"  as the timeline, select all iterations, and then pick team "": the resulting chart shows "0" points for each iteration. However, the plan view for the iteration immediately under the "new" timeline and owned by team "" shows 2800 points, which is the correct number.

If I go back to the "Work Item Categories" for the project and change the mappings for <any timeline> to map category "Development" to team "" instead of "T.current", then the chart works.

Somehow when I pick both team "" and timelime "new" in the chart selection criteria , it only considers stories where the categories ("Development" in this case) are assigned to team "" in the <any timeline> in the "Work Item Categories" tab of the project definitions.

To me that is a bug, as it should consider the categories assigned to team "" in the same timeline I chose for the chart.

I am on RTC server 4.0.1, build id RJF-I20121109-1457

Be the first one to answer this question!

Register or to post 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.