Filter custom workitem type from plan
Hi,
I have a new kind of workitem - using it as a "reflection" of other workitem and thus - need to use the same "planned for" filed. e.g., I have a "defect" planned for iteration1 and "defectReflection" planned to this iteration too. (they are linked by "depend on" - "blocking" link) My problem is that I see it in the plan. I want to see only defects in the plan and not "defectReflection" workitem kind. Thanks, Moti |
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 01 '09, 10:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Could you say a bit more about what you want to use the "reflection"
work item for? It might be an instance of the kind of "stateless record" requested in work item 100617. Cheers, Geoff motiwert wrote: Hi, |
This is a normal workitem type, I call it "reflection" only because this is the context I'm using it. The defect contains the data for the development team and the reflection contains the data for the customer support team.
This type is other category than defect's and it has it's own workflow and attributes. Using the API, some custom scripts are transferring data from the defect to the reflection wokitem. But, again, it's a normal custom workitem. Could you say a bit more about what you want to use the "reflection" Hi, |
Geoffrey Clemm (30.1k●3●30●35)
| answered Dec 02 '09, 11:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
That makes sense (in fact, I requested built-in support for something
like this a while ago in work item 21879). I've submitted work item 100783 to allow you to declare that a work item type is neither a plan item or an execution item (please subscribe or add comments to indicate your interest/support for that work item). Cheers, Geoff motiwert wrote: This is a normal workitem type, I call it "reflection" only |
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.