Welcome to the Axosoft Community, Sign in | Register | Help
in Search

Importing From FogBugz into OnTime

Last post 09-08-2009, 5:12 PM by Sean McHugh. 0 replies.
Sort Posts: Previous Next
  •  09-08-2009, 5:12 PM 19374

    Importing From FogBugz into OnTime

    Q: I'm performing a migration from FogBugz to OnTime and was wondering if there were any scripts available for this.

    A: Axosoft hasn't developed any scripts for this purpose but a member of our community did and he was kind enough to share this with us. These scripts are not Axosoft's and we don't support them but if you find them useful, feel free to stop by THIS thread and thank Brian for his trouble.

    You can find the scripts HERE and you'll find the instructions that Brian provided below

    There are  4 SQL scripts, one for each related area in OnTime that you would potentially run to pull data from FogBugz (Bugs,Features,Support,Tasks.) The queries are all fairly similar and change only to reflect area/category of data you want to pull. The first insert is used to narrow down query results by category (Bug=1, Feature=2, Inquiry=3) and we also used it to include or filter out specific releases (FixFor). The release filtering can be removed if not needed. The select statement on the lower half is actually selecting the data, mapping FogBugz values to valid OnTime values, with the resulting data being copied/exported into Excel using the Template.xlt file or a CSV file you create too match your query results. The following fields in that select statement you will want to customize to your existing FogBugz environment and mapping how you want them to show up in OnTime:

     

    ixProject (project ID, we used the Project field to track our software products/projects)

    ixPriority (mapped to OnTime priorities accordingly)

    ixStatus (Status used for workflow routing in FogBugz but we did not map these directly to OnTime workflow items, used to determine OT status)

            (the OnTime Status could also be determined/mapped by using the open/closed/resolved date fields if desired)

    ixFixFor (release ID, we used the FixFor field to track the releases of our products/projects)

     

    You will need to tweak the scripts to fit your needs. Not a lot of documentation in the scripts but hopefully this helps. One thing I will note.. When the description field is imported it loses all of the formatting, making it a pain to read but the data is at least there (o.output). We simply reformatted the more recent items as we accessed them in OnTime.

    Regards,
    Sean McHugh
    Axosoft Support
    Click HERE to take our support survey.
View as RSS news feed in XML

© 2002 - 2007, Axosoft, LLC. All Rights Reserved. | Privacy
Bug Tracking | Defect Tracking Videos | Help Desk Software