RTC work item query to export parent created in previous plan
Why Tea (25●2●4●6)
| asked Apr 29 '13, 9:18 a.m.
edited Apr 29 '13, 9:21 a.m. by Ralph Schoon (63.5k●3●36●46)
I have a rather straightforward RTC query to export work items as below.
1) Team Area is: xxx
2) Planned for is: Current Iteration (picks up default plan)
3) Type is: Defect, Task, Story, Epic, Impediment, Retrospective
This work fine if the child and parent work items were created in the same plan. But if a Task is continued from previous plan, it's parent Story will not be exported. Is there a way to set up an RTC query so that a child work item's immediate parent is always exported regardless of when they were created?
Thanks!
/Why Tea
|
3 answers
Hi,
Can you double check your child Task? Does it still have the parent link after it was transferred to new plan?
According to this enhancement, the parent link will break. I am wondering if this is the cause for you not being able to export parent Story...
|
it depends on whether there was a COPY made to a new workitem to continue. THAT is where the parent link was NOT copied to the new workitem..
the parent link of the original workitem should not have changed, and so you can include the Parent Link workitem in the query output by selecting the parent Link in the query builder.. (you may have to Show Links in the builder UI) and technically this has nothing to do with 'Plan'. you asked for Current Iteration, regardless if there is a 'plan' above it. A Plan is (organized) Work (workitems) done by People (Team) over Time (Iteration) |
|
Hi Sam,
When I continue a task in the next sprint, it's (parent) story shows:
I believe the parent link is copied with the work item (task).
I managed to use a workaround to get what I wanted by using a second query:
1) Team Area is: xxx
2) Planned for is: Current Iteration (picks up default plan)
3) Type is: Story, Epic
4) Children > Planned For > Start Date after (including)
- here I specify the date of the current sprint
With this query, I managed to get the stories for all the tasks in the current sprint.
I then paste the stories (parents) to the tasks (children) and run a VBScript to pair up the child-parent work items.
Kind of messy, but it works. Would be nice to be able to do in just one query.
/Why Tea
|
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.