How to use Plastic SCM and TechExcel DevTrack I
As you may have already seen on previous post, Plastic SCM provides with the option of using it integrated with different task tracking tools as it integrates with some of the most extensively used systems in the market, you can have a look at the list of options here.One of them is TechExcel DevTrack!
On this post I am going to explain with examples, how to use Plastic SCM integrated DevTrack.
First of all we have to know that Plastic SCM not only integrates with this system, but also offers customizable options for the integration.
Why do we provide with different options? So you can use the one that better adjusts to your working pattern: Let´s see the “Task on Branch” working mode on this post.
The first step in order to set up the DevTrack extension on your client machine you have to copy “devtrackextension.dll” on the folder where Plastic SCM client is installed and add the following lines (circled in red) in order to indicate the client to use this extension:
And you would also need to create a file “devtrackextension.conf”, its appearance by default is the following one:
<devtrackextensionconfiguration >
<dtlinkplusurl>
http://192.168.1.237/LinkPlusWebService/WSDTIncident.asmx
</dtlinkplusurl>
<user>terry-j</user>
<projectid>daveProject</projectid>
<systemid>daveSystem</systemid>
<branchprefix>issue</branchprefix>
<dtbuginfobrowserurl>
http://192.168.1.237/scripts/texcel/devtrack/buginfo.dll
</dtbuginfobrowserurl>
</devtrackextensionconfiguration>
Finally, you need to make sure that:
the devtrackextension.dll file is on the Plastic SCM client folder.
And by default the “Task on Branch” option is set, or you can specifically set it as follows:
<devtrackextensionconfiguration>
<dtlinkplusurl>
http://192.168.1.237/LinkPlusWebService/WSDTIncident.asmx
</dtlinkplusurl>
<user>terry-j</user>
<projectid>daveProject</projectid>
<systemid>daveSystem</systemid>
<branchprefix>issue</branchprefix>
<dtbuginfobrowserurl>
http://192.168.1.237/scripts/texcel/devtrack/buginfo.dll
</dtbuginfobrowserurl>
<workingmode>
TaskOnBranch
</workingmode>
</devtrackextensionconfiguration>
Now that the extension is set up:
The first step to start working with it would be creating a new bug on our task/bug tracking system; DevTrack in this case.
In DevTrack tasks can be submitted as either defects or new features, and they can also be classified into several categories such as Minor Improvement, Future Enhancement, Discrepancy Report, etc.
As the new task is created, it is on state “NEW” and assigned to a developer. “The title given to this new task is "Additional options: Customization".
By saving the task we can see the number D given to it, in this case it is issue number 106, and we could indicate the system to send an email to the developer in order to let him know that we have assigned him a new task.
When the assigned developer, in this case Paul, is ready to start working on task 106, he will easily create a new branch and name it according to the task created on DevTrack, and add his comments accordingly.
You can also set the branch base and it will be remembered by the branch every time a user switches to work on it... if you are interested on learning more about Plastic smart branches you can find it here.
After the branch has been created, by going to the top left on the branch view we can display the extended information of branches, which will show information on the DevTrack related bug when selecting a branch.
On the following image we select the newly created branch /scm00106 and on the right hand side we can immediately see the information of issue 106 on DevTrack: its ID, owner, title and comments are shown on the custom view:
And as soon as the task is accomplished we double clicking on the dialogue or just click on the extension button, which will take us to the DevTrack tasks, where we can change the status, which will be refreshed on Plastic:
Easy!, Hope you like it!
0 comentarios: