[p4] Anyone used StarTeam bug tracking in the past?
jsmith at medplus.com
Tue Mar 22 05:55:49 PST 2005
We had a business unit that was using StarTeam and we are in the process
of converting them to Perforce. All they used StarTeam for was code
management so I can't speak to the defect tracking aspect. However,
unless they've made significant performance improvements since version
5, I find StarTeam significantly slower than Perforce.
If the "one stop shop" aspect of StarTeam is what's driving the
decision, I suggest you look at one of the defect tracking systems that
are integrated with Perforce. The two I know of are Bugzilla (free) and
TeamTrack (pricey but good). There is also an SDK (P4DTI) that will
allow you to build your own.
From: Shenon, Amanda [mailto:Amanda_Shenon at g1.com]
Sent: Monday, March 21, 2005 5:52 PM
To: perforce-user at perforce.com
Subject: [p4] Anyone used StarTeam bug tracking in the past?
We are in a final decision process between Perforce and StarTeam. I am
the Perforce advocate at our company and I am trying to solicit some
competitive information. It seems that the integrated bug tracking in
StarTeam is making some people lean towards it. Have any of you used
StarTeam and it's bug tracking in the past? Any comments on how well it
worked (especially compared to other commercial bug tracking tools) or
any problems or limitations with it? I am hoping this will help me get
Perforce in the door here! I am much more a "best of breed" proponent.
Thanks a lot for any info!
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the perforce-user