http://blogs.msdn.com/hippietim/archive/2006/04/07/570998.aspxWe have a number of scenarios we'd like to enable in future releases of Visual Studio Team Foundation that would really benefit being part of a generalized workflow framework. Things like code review/checkin processes, build release and staging, etc.en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/hippietim/archive/2006/04/07/570998.aspx#571478Sat, 08 Apr 2006 13:36:47 GMT91d46819-8472-40ad-a661-2c78acb4018c:571478davidacoderWell, I feel you guys could ditch your custom work item store and use WSS3 as your work item engine. They have complete support for different content types within one list (ie work item types), workflow based on the workflow engine, Infopath smart client edit, web browser form edit via Infopath server side and everything would be nicely integrated into the sharepoint portal. Have you thought about that?http://blogs.msdn.com/hippietim/archive/2006/04/07/570998.aspx#572465Mon, 10 Apr 2006 16:20:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:572465Team System NewsThe TeamPlain Team System blog links to a MSDN Virtual Lab: Managing Work Items with TeamPlain Web Access....