Importing Bugzilla from Devzing to JIRA

Excrubulent May 24, 2013

I'm trying to import data from a Bugzilla instance hosted on Devzing. Devzing uses Bugzilla 4.2.5, which is not officially supported by the JIRA importer. Also, I don't know what SQL backend Devzing uses, and the connection details (eg: port number) are obscure to me as well. Is there a way to get this to work?

I can download my database as a .sql file, so if they can be imported or converted to a useful format, I may actually prefer that option.

3 answers

1 accepted

1 vote
Answer accepted
Wojciech Seliga
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 26, 2013

Hey,

We haven't tested JIRA Importers Plugin (bundled with JIRA) against Bugzilla 4.2.x, but we haven't head from customers about any problems with it, so most probably it will just work for you fine.

I doubt you will be able to connect directly to Devzing SQL DB where your data is kept (firewall, etc.). I would recommend downloading your DB as SQL file. Perhaps from this SQL dump you will be able to deduct easily what kind of DB Devzing uses. If not, then I recommend asking them and they hopefully should just tell you. Then you should import such SQL dump into the same (or similar in terms of the version) DB run by you locally. Once it's ready, then connect from JIRA to your local Bugzilla DB and it should work.

Please note, that Bugzilla may keep big attachments outside of its DB ("Big File" - http://www.bugzilla.org/docs/3.0/html/attachments.html). If it's the case for you, you would have to also ask Devzing to give you the access to your files (some kind of dump) and then you would have to set up also whole Bugzilla locally - as in order to import "Big File" Attachments JIRA needs to connect not only to DB, but to the regular Bugzilla instance via its remote API. If you don't use Big File attachments stored in the filesystem, then you don't need to setup Bugzilla locally. It would be enough to connect directly to your cloned DB instance.

I hope it helps.

Cheers,

Wojtek

Excrubulent May 26, 2013

Well, there are no attachments whatsoever. Which is good, because setting up Bugzilla to work on my local system would take more work than just manually entering the bugs into JIRA, in my experience. If I get an answer about which DB they use, I'll come back here with the information.

0 votes
Tamir Lavi July 11, 2013

Hi,

Did anyone had a success in importing from Bugzilla 4.2.5 ?

I'm trying to perform am import from Bugzilla 4.2.5 hosted on Amazon AWS.

I openned the connection on port 3306, and created a user that can login from the outside.

I also verified that I can login to the database from the local mysql command line.

Yet - I keep getting "error connecting to database" when I perform the import.

Could it be the this error indicates for the lack of support in 4.2.5?

Excrubulent July 11, 2013

This sounds like a separate question, rather than an answer to this question. You might get more success with this issue if you post it as such.

Tamir Lavi July 11, 2013

I did!

Here:

https://answers.atlassian.com/questions/187761/importing-from-bugzilla-4-2-5

But Renjith sent me over to this questation... :)

Anyway - I had no luck there eather.

Excrubulent July 11, 2013

Ah, I see. I'd like to be able to tell you I had success, but I actually haven't tried yet. Other things getting in the way :(

0 votes
Excrubulent June 6, 2013

Just following a conversation I had with Devzing, they use MySQL 5.6. That's probably subject to change, so I'll add that this information was current as of 30 May, 2013. Still haven't tried the conversion, though.

Suggest an answer

Log in or Sign up to answer