Shacharpr Posted February 22, 2013 Report Share Posted February 22, 2013 Hi In my company bugs are tracked using HP QC system as defect entities. Development stories/task are managed in a Kanban Board. We are considering to implement the branch per task approch using Plastic. Since the branch is 1:1 with task and is extendible using the attributes, we wonder if we need issue tracking system in addition. Does anyone has exprience with such a scenario? Will love hearing the fourm exprience and opinion for pros of having issue tracking system when working branch per task approch. Thanks. Link to comment Share on other sites More sharing options...
calbzam Posted February 22, 2013 Report Share Posted February 22, 2013 Hello, You are right, branch per task methodology fits really good with issue tracking systems. You will probably enjoy this post explaining how to fix a bug branch per task way: http://codicesoftware.blogspot.com/2010/11/fixing-bug-branch-per-task-way.html Plastic doesn't include a bug tracker by default, but you can integrate some of them. The documentation explains how configure issue trackers with Plastic, it's very easy: http://www.plasticscm.com/releases/4.1/manuals-html/en/extensionsguide.htm If you have problems configuring an issue tracker with Plastic or more questions don't hesitate to ask. Best regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.