Modifying the Closed group

Hello bootooty,

I believe RTC uses the closed group for reporting as well as for planning
and queries. For example in your case reports and queries as well as the
iteration plan would count Verified and Resolved workitems as still open.
The iteration plan would not gray these out reports that use the closed group
would show different results etc.

However, I can imagine that workflows with just one state in the closed groups
may make sense for some work item types.

Ralph

Currently, the "Closed" group applies to the states of: "Closed",
"Verified" and "Resolved".

Will modifying the "Closed" group to apply only to the state of
"Closed" affect other areas of the UI - ex. burndown chart?

As a follow on then, will RTC 2.0 allow for "customization" of the iteration plan tab?

If we leave the "Closed" group alone, a quick glance at the iteration plan shows strike-thru's on IDs for all of the closed group. This does not give a clear picture to work items actually closed. We could either change our closed group to be just closed items (strike-thru appears then only on closed work items) or wait for RTC 2.0, assuming it will allow us to add the status column to iteration plans. Or maybe a color-code option?

If the feature is coming, can you reference the work item?

Thanks

Hi all,

I'm also quite interested in this topic. My question is "What defines if a work item is /"? Like on a plan (strike-through on closed items) (filter: exclude resolved work items), or a query (select resolved work items).

I've been trying to change the basic flow of the "Scrum" template, so only "Verified" is "Closed" / "Resolved". I've done the following:

- changed "resolve action" to "verify"
- removed "show resolution" from "resolve"
- removed "set resolution" from "resolve"
- moved "resolved" to "In Progress".

But still defects in "resolved" state shows up as "Closed" / "Resolved".

Anybody have a comment on this?

So I've been doing some testing, and it seems, that if I create an entirely new state "Resolved" instead of the original one, then RTC actually behaves as expected with the "Closed" group.

Any comments anybody?

I have a customer experiencing this exact same problem.

I tested in RTC 3.0 RC2, and it exhibits the same behavior.

Has anyone opened a defect/enhancement on this?

Gary

I have a customer experiencing this exact same problem.

I tested in RTC 3.0 RC2, and it exhibits the same behavior.

Has anyone opened a defect/enhancement on this?

The group that a state belongs to can be configured:

http://dl.dropbox.com/u/2663305/ScreenShots/2010-11-11_1520.png

--
Regards,
Patrick
RTC Work Item Component Lead

Patrick,
Now that we can configure the group that a state belongs to...

1) Is it possible to create a query to return all the work items belonging to a specific group? If so, how?

2) Some out of the box queries filter work items based on status is "resolved" (or "unresolved"). How is this criteria tied with the groups?

Any document/link where we can read more about this topic would be appreciated.
Thanks!

--Claudia