1 follower Follow

Can I use the project history?

According to an article (or post) from Matt Terski, there is currently(?) no way to load a previous version of a project directly in Case Complete. The information in the article indicates that this would have to be done through the version control system. Since we are using CC'd embedded version control, I'm wondering if someone can help me out.

What I would like to do is to be able to load the project and all the appropriate package files as of a given date.

How do I find and load a previous version of the project?

I've looked in the Tortoise Repo-browser. I can see versions of files, including the overall project file (.ucd). When I look at the dates, I see a version from 7/8, followed by a version from 7/22, and I know that a lot of work has been done in the intervening dates. I'm assuming that work is captured in the individual packages files (.ucp).

My problem is that I am trying to use information from CC to report statistics on requirements "churn," i.e., the number of requirements added and the number of requirements changed. I can use DateAdded and DateModified, but, since that only provides a snapshot, I lose any interim modifications. If a requirement was added on 6/1, modified on 6/6, again on 6/16, I would like to be able to illustrate that fact.

Anyone got any thoughts on whether this can be handled and how?



Tom Tomasovic Answered

Please sign in to leave a comment.

1 comment


Hi Tom! That's right – there’s currently no way to load previous project versions directly within CaseComplete. comes the closest - it keeps track of what changes with every upload. If you fail to upload each time a change is made though, you might not get an accurate picture of how often an item gets changed, since multiple changes could be rolled up into a single version of that item.

However, we think what you're doing should be possible with TortoiseSVN.

In the repo-browser, right click on the folder itself (i.e. on the left side of the window), not on an individual file, and select show log on that. There you can browse each revision including the date, which files changed for each revision, and checkin notes if they were supplied.

When you find the revision you’d like to revert to, right click and select export, then provide a new folder. This will save all the project files as they were on that date. You’ll of course need to be careful of the scenario where two packages have interdependent changes, but were checked in separately (and therefore will have different revision numbers), e.g. when moving an item from package A to package B - make sure that you revert to the modified versions of both A and B.

Once you’ve got a specific version exported, you can open that up (from your new folder) in CaseComplete.

Standard caveats apply, of course: TortoiseSVN is a third-party program, so we can't be held responsible for data loss, its support or use, etc.


Jason Payne 0 votes