A forum for technical support discussion related to Fogbugz.
Does anyone have any experience or pointers in moving existing work items from Project Tracker/collabnet to FogBugz?
I am looking at porting items over on an initial data load and then moving forward with FogBugz from there. Ideas around collabnet in particular would be great, but working approaches from other tracking systems would be helpful as well.
When we migrated to FB, we took these steps:
- Data struct analysis of FB internally
- A dozens of passes using a custom piece of code to import into FB until we got it right.
It was a lot of work, but we got it right.
That was a few years ago. There may be better ways to go now.
Sunday, September 13, 2009
Here's the FogBugz database schema documentation:
We're very happy to answer any questions about FogBugz's schema or operation. We recommend using the API to make the move.
If you're going to be on FogBugz On Demand, it's probably best to purchase a license or two for a manual install. This'll allow you to blank out the database at will while you're getting things right.
We can refund any purchase or simply credit it to On Demand, within 90 days.
This topic is archived. No further replies will be accepted.Other recent topics