Fog Creek Software
Discussion Board




PVCS Tracker, anyone use it?

I am looking for opinions on PVCS Tracker, because we use that here on a project I am involved with.

I noticed that it appears to be more of a toolbox than an actual tool, but that may be the way we're (ab)using it here.
We have all kinds of fields that need to be filled and that are mainly for the purpose of project management, not bug solving.

But the worst thing is that it does not provide any workflow. Moving a bug forward means manually selecting from a list of possible states that a bug might be in, with all doors open to input errors, and with the additional requirement that you now also need to concern yourself with the meaning and flow of bug states.

I find that questionable, because you want the tool to take care of that. However, some people here seem to think its a good thing and that it is the responsibility of everyone to know how to move a bug around and do it correctly. I won't go into what I think of that, because I want to keep up the appearance of being a respectable person...

But now I am curious, is this an inherent flaw of PVCS Tracker, or is it really a good tool, say compared to Fogbugz, but simply misunderstood by me, or abused by the organisation. Please don't jump immediately to the easy conclusion of the latter, but provide some thought on the first too, please...

Practical Geezer
Wednesday, May 14, 2003

I demo'ed it and the main thing I didn't like is that it didn't really present an issues history when you view a bug record.  I like it more like Fog's product where you can see the whole list of comments as it the record moves from state to state.  Also, many of the fields always seemed to be scrolled off of the bottom of the page, where they could be forgotten.

Keith Wright
Wednesday, May 14, 2003

We unfortunately use PVCS, and I can confirm that workflow does not exist and you need to RTFM in order to do anything, and we all love doing that ;-)

It is almost so bad that we have resorted to tracking our internally detected bugs separately so as to avoid that hassle on going through PVCS.

Pathetic Version Control System devangelist
Wednesday, May 14, 2003

PVCS Tracker is a tool box.  And if you have a decent idea of where you are going and pay Merant several grand on training and additional several grand for on-site specialist to set it up, then you can have a usable product.  There is NO AUTOMATED WORK FLOW in Tracker (I ought to know,  I manually change a state flag every time I build to let test know they have work). We made it part of the development process that when your defect has change state, the person doing the change places a field in Tracker to the correct state.  As the build guy I get to move stuff from ready to build to ready for test (Oh the fun).  The only tools that do the Autowork flow either are intergrated with a source control tool (PVCS Dimentions) or can Intergrate with a source control tool (ClearQuest and ClearCase)
All of which are expensive (I do not know every CM tool out there so there might be tools that do work flow with out the cost).

A Software Build Guy
Wednesday, May 14, 2003

We're using the i-net thingy, and most of my Tracker work is changing state attributes... It's like that by design. We have a set of rules that everybody follows, and that's how we get things done.

It's not perfect, but it works. I don't complain, because we used to use Excel before.

YF
Friday, May 16, 2003

You can work with it. The real problem with the tool is the
administrative side. For example - the backup/restore
feature really sucks (I know from personal experience ...)

Liron Levy
Saturday, May 17, 2003

Last communication on this topic is about a year old and I didn't get the release/version of what Merant's (now Serena) PVCS issues were. We only have Version Manager 7.5.1 and have yet to upgrade to 8.0. We are in need of a bug tracker and were considering Tracker (if not some other tool). I would appreciate any 8.x feedback on Tracker: it's administrative use as a toolbox (if not a tool), any workflow automation, backup/restore working, any other "flaws" or improvements from the previous version, etc. Thanks in advance for your response... 

Ron Castaneda
Tuesday, June 15, 2004

*  Recent Topics

*  Fog Creek Home