Geeks With Blogs
The Caffeinated Geek Tech Obsessed in Winnipeg

I’ve been travelling with my buddies Etienne Tremblay and Wayne from Microsoft all over the world talking to project teams about using VSTS and TFS. [See Etienne’s Blog for the chronicles of our trip] One topic that inevitably comes up is the fact that work items can’t be deleted. Normally, I totally agree with this practice. If a workitems was created with intent, then it should run it’s lifecycle. However, since managing projects with TFS can driven using the warehouse metrics and reports, it becomes problematic when workitems are created accidentally and can’t be deleted. I’ve considered adding a ‘deleted’ state to some of the workitem types (especially task) and filtering out the ones marked ‘deleted’ from the queries. However, I’m worried that this will add significant overhead to queries to include the ‘not deleted’ condition. Also, it’s unclear what adding this state would have to reports within the TFS. I haven’t taken the time to look through all the reports to determine whether results would be misleading by adding this new state.

Has anybody out there considered this solution? If not, how are you addressing these mistaken work items?

Aaron

Posted on Monday, June 26, 2006 1:04 PM Visual Studio | Back to top


Comments on this post: How to handle unwanted Work Items in TFS

# re: How to handle unwanted Work Items in TFS
Requesting Gravatar...
Thi think you can maked them as
State=closed
Reason= obsolete
Left by note sure on Jul 24, 2006 10:51 AM

Your comment:
 (will show your gravatar)


Copyright © Aaron Kowall | Powered by: GeeksWithBlogs.net