0

I am using the method described by Herb Caudill here to import our basic list of bugs from an excel worksheet. Everything works great except for a couple of things that aren't described in his method. 1) I would like to be able to import resolved bugs as resolved and 2) The dates and certain other settings that I am importing don't seem to be "taking" (the dates could be a formatting issue, not sure)

I keep slowly adding properties to the command, but no matter how i set them, here are the symptoms I'm experiencing directly after import.

a) The task always imports as status=active b) fOpen always = 0 c) ixPersonOpenedBy always equals ME d) ixPersonResolvedBy and ixPersonClosedBy always = 0 e) ixStatus always = 1 f) dtResolved and dtClosed are always NULL g) dtOpened is always the current time

Am I trying to set things that can't be set on import or am I missing something in my command? Thanks.

flag

3 Answers

1

Check out my answer to this question for some pointers on how to set the ixPersonOpendBy and dtOpened. I think you'll end up needing to use separate commands to open and resolve the case.

link|flag
Thank you James. Your answer paired with help from Rich worked like a charm. – Kevin Foley Aug 18 2010 at 2:30
2

All: I found that the answer above worked perfectly, but wasn't facile enough for my client, so I wrote a VB application that does the trick. Also, I wrote it so that it pulls straight from the Excel spreadsheet, so no export is needed.

It's in Beta, currently free for trial. http://devshed.us/Products/FogBugzCaseImporter.aspx

(Please up vote this answer if you found it helpful)

link|flag
This worked great for me! – Chris Phillips Nov 23 2010 at 22:40
1

I had trouble with this recently. One side note is you must be logged in as an admin to do any sort of importation.

Per James, make sure you're using dt, and ixPersonEditedBy to specify the historical date and actor.

I recently discovered that if you want to do multiple edits or resolves, you don't actually have to get the bug number back from the API when you do cmd=new. You can actually just give it the ixBug when you create it, and on subsequent actions. Thus:

cmd=new&ixPersonEditedBy=3&sTitle=foo&ixBug=1234&dt=2001-01-01

cmd=resolve&ixPersonEditedBy=4&sEvent=done.&ixBug=1234&dt=2001-01-02

cmd=close&ixPersonEditedBy=4&ixBug=1234&dt=2001-01-03
link|flag
When you do specify the ixBug, make sure you do them in numerical order, smallest to largest. If you try to do an ixBug number smaller than any existing ixBug numbers, the autonumber takes over and assigns it the latest autonumber instead. – Chris M Jan 11 at 23:04

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.