Problem using Velocity viewlet

Context: RTC 2.0

When I configure the velocity viewlet for a team that has known, completed stories over several iterations I get the message in the viewlet:

"No closed story work items were found."

Yet for the team that I have chosen when I run a query of:

Filed Against = "team x" AND
Type = "story" AND
((status = Default Workflow/Closed) OR (status = User Story Workflow/Done))

my query returns 35 work items, all with a status of "Done".

I am thinking that the key is in "Done" vs. "Closed". Does the velocity viewlet assume that the terminal state is "Closed"?

Bump

On 11/30/2009 1:38 PM, klzemanek wrote:

klzemanekwrote:
Context: RTC 2.0

When I configure the velocity viewlet for a team that has known,
completed stories over several iterations I get the message in the
viewlet:

"No closed story work items were found."

Yet for the team that I have chosen when I run a query of:

Filed Against = "team x" AND
Type = "story" AND
((status = Default Workflow/Closed) OR (status = User Story
Workflow/Done))

my query returns 35 work items, all with a status of
"Done".

I am thinking that the key is in "Done" vs.
"Closed". Does the velocity viewlet assume that the
terminal state is "Closed"?

Bump

The Team Velocity viewlet doesn't assume the terminal state is Closed -
it can be any state which falls into the "closed states" state group.

What is the "Planned For" field on these stories? The Team Velocity
chart should show one bar for each iteration, with the height of the bar
equal to the number of story points represented by closed stories
planned for that iteration.

james
RTC Reports Team Lead

The Planned For field contains the name of an iteration. These are past, completed iterations. Just so that I am clear, I don't get the bar graph - I just get the message "No closed story work items were found."

Thanks to James' kind assistance I have this working. The problem was that the "Complexity Attribute" had not been set. Apparently new to RTC 2.0 this allows an abstraction for projects not using story points. But even if you are using story points you need to configure this setting in order to get the reports working correctly (Suggestion: how about setting this to story points by default?). To set the complexity attribute:

Open the rich client
Open your project and go to the Process Configuration tab
Expand Project Configuration->Configuration Data->Planning
Select Plan Attributes
Select a complexity attribute (mine was Story Points) and give it an abbrev (i.e. "pts")
Select Top-Level Work Item Types
Verify that "Story" is selected as a Top-Level Plan Item Type
Save

Now my story point-based reports (which are actually "complexity attribute-base reports") work correctly.

Thanks again James.

Sorry to be continuing an old post, but this is exactly the problem we have as well. Except our complexity is already set to story points. Is there anything else to try before we open a PMR?