[p4] Recommended bug tracking tools
Shawn Hladky
p4shawn at gmail.com
Mon Sep 24 11:45:10 PDT 2007
>>Hay, have you (or anyone else) integrated TeamTrack with Perforce? How
well
>>has that gone and how does it work from a process perspective? Like, what
>>kinds of functionality does the integration enable from a process
>>perspective?
We have a home-grown integration that queries the TeamTrack db directly and
populates jobs in Perforce. It's a relatively simple integration, but quite
effective.
The process works as follows:
1. Integration creates job from TeamTrack issue.
2. Developer has a job-view like Owner=<username> State=In_Development
3. When submitting through the GUI, the developer has check-boxes for all
issues assigned to them.
4. Developer checks the correct issue and submits (p4 trigger enforces)
5. Developer transitions the issue in TeamTrack (filling in the required
fields).
P4DTI didn't work for us because of complicated workflow rules in
TeamTrack. We initially intended to add the reverse integration (transition
TeamTrack issues on submit from P4), but we found that hopping into
TeamTrack wasn't a huge burden, and it allowed for much more flexibility to
update fields, comments, etc. The critical data, what code fixes an issue,
is stored through p4 fixes.
On 9/24/07, Brian Jones <caneridge at gmail.com> wrote:
>
> On 9/24/07, Smith, Jeff <jsmith at medplus.com> wrote:
> >
> > Actually, I just attended the user meeting for our region and this is
> > definitely not the case. Serena is pushing ALF 2.0 and web-services
> > compliance. They strongly delivered the message that they believe the
> > days of trying to sell products as a proprietary tool-chain are over.
> > They seem to understand that companies have to acknowledge that
> > integration of tools is a must-have for the consumer. They've already
> > put their money where there mouth is by adding pretty good web services
> >
> > Jeff
> >
>
>
> Jeff,
>
> That's nice to hear. I guess my worry is that they will prefer their SCM
> solution over that of other vendors. I would be more accepting of a
> message
> like that from a vendor that does not have sell competing tools to that of
> other vendors they intend to integrate with. The real test is if one can
> integrate integrate say Perforce into TeamTrack to the same degree that
> the
> Serena version control tool integrates into the product.
>
> Hay, have you (or anyone else) integrated TeamTrack with Perforce? How
> well
> has that gone and how does it work from a process perspective? Like, what
> kinds of functionality does the integration enable from a process
> perspective?
>
> Brian
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
More information about the perforce-user
mailing list