Defect Tracking across projects

we have started playing around ts, , have questions around best practices bug , requirement tracking in our environment.

we add functionality our product on project project basis, there may defects or requirement requests not completed in praticular project.  best way track these.  can move them project project?  may example make easier understand.

our product named widget.  have project add features, , create widget 2.0.  after widget 2.0 project have widget 3.0 project.  generate bugs , requirements while doing 2.0 project.  once project complete, filed bugs , issues on 2.0 well.  start 3.0 outstanding bugs , feature requests 2.0.  make more complicated, have widget 2.0 customer a, , widget 2.0 customer b.  core product widget 2.0, there customer specific features company a, , company b.  there widget 2.0, comapny project, , widget 2.0 company b project.  later there widget 3.0 company project, , widget 3.0 company b project.

 

what trying figure out best way set these in team system.  if set new project each instance, how persist bugs , requirements not addressed?  make more sense set widget core project, , company a, company b project, , have later versions new areas?

 

anyone have thoughts on this?

 

thanks!

 

paul

what suggest have 1 team project.

i think should create project per product. because want track whole lifecycle of product , not 1 version.

working different versions should solved picking right branching , merging strategy. use areas , iterations define different features , different iterations going implement them.

i use branch purpose model , create branch after shiped specific customer. can keep brach maintain specific version use merge between different brances reverse or forward integrate additional fixes or features other branches.

you can move workitems later iteration (or release if want) , work same items.

if want project per version, way keep item copy 1 project other , reschedule there.

you should start new project if need manage different project. if not keep same project , make sure implement correct configuration management plan within tfs version control.

hope helps,

marcel

Archived Forums V  >  Team Foundation Server - Setup and Administration