Search Sort Posts:  Oldest to newest Newest to oldest

06-19-2008, 7:51 PM cmcleod Joined on 09-19-2007 Minneapolis, MN Posts 18 WorkItem migration tool filter First off thanks for releasing the tool to help us out. I'm excited about offering a solution that doesn't involve manual work and manual mistakes :) I'd like to know if it is possible to filter the work items being converted. My first conversion attempt failed on closed sprint retrospective items and I don't care about those so I'd like to filter them. If it is possible is it done in the WorkItemSort.xslt file? Let me know.    Report

06-20-2008, 8:58 PM cmcleod Joined on 09-19-2007 Minneapolis, MN Posts 18 Re: WorkItem migration tool filter I've started getting this error: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. any ideas?    Report

06-23-2008, 7:12 PM cmcleod Joined on 09-19-2007 Minneapolis, MN Posts 18 Re: WorkItem migration tool filter a reboot of the server took care of that issue. It was windows related anyway. I managed a crude filter by changing the template match from <xsl:template match="WorkItem"> to <xsl:template match="//WorkItem[Classification/System.WorkItemType!='Sprint Retrospective Item']">. I did this because it kept failing on sprint retrospective items. I'd like to filter out even more now. If I delete the XML files from the export process before a date of my choice will it just import what is left?    Report

06-24-2008, 8:54 AM Crispin Parker Joined on 11-13-2007 Posts 664 Re: WorkItem migration tool filter Hi cmcleod, Sorry for not picking up on your thread sooner. Looks like you've made good progress already. In answer to your question: If I delete the XML files from the export process before a date of my choice will it just import what is left? Deleting the any of the xml export files will most likely cause an error. The files need to be applied in the correct chronological order. This is to ensure that the work items are created in the same sequence as original project. Work item linking depends on the existance related work items, so if they don't exist in the project an exception will occur. Hope this helps. Regards, Crispin Parker, Technical Consultannt, Conchango. "It is better to light a candle than to curse the darkness"    Report

Scrum for Team ... » Version 1.2 - T... » Scrum for Team ... » WorkItem migration tool filter

(please select) Forums Home |- Search Forums |- Active Topics |- Unanswered Posts User Options |- Sign In |- Join this community |- Forgot Password Scrum for Team System |- Scrum for Team System - Announcements |- Scrum for Team System - Feature Requests |- Task Board for Team System Beta Discussions Version 2.x - Team Foundation Server 2008 |- Scrum for Team System - v2.x Support |- Engineering Practices – v2.2 Reports Version 1.2 - Team Foundation Server 2005 |- Scrum for Team System - v1.x Support