JIRA migration to bugzilla

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

JIRA migration to bugzilla

Merlijn van Deen
Hello all,

Today, I hacked together a JIRA migration tool. If you want your bugs migrated please do the following two things:

1) Under Administration, <your project>, People, add 'Bugzilla Bug Exporter (valhallasw)' to 'Administrators' and click 'Update'. Otherwise, the bot cannot close the bug.


3) Your bugs will be migrated for you! See https://bugzilla.wikimedia.org/58820 for an example of what the converted bug looks like.

Merlijn

_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Reply | Threaded
Open this post in threaded view
|

Re: JIRA migration to bugzilla

Tim Landscheidt
Merlijn van Deen <[hidden email]> wrote:

> Today, I hacked together a JIRA migration tool. [...]

As I said on Bugzilla: Pretty cool! :-)

If someone is just interested in a backup of their project,
but doesn't necessarily want to migrate it to another bug-
tracker (yet), JIRA provides XML dumps that look fairly com-
plete.

To download one, go to
https://jira.toolserver.org/secure/QuickSearch.jspa and type
in for example "project = ".  An autocompleted list should
show up.  Choose your project and click "Search".  At the
top right you should see a drop-down menu "Views".  Choose
"XML", save the file and look if it contains everything you
expected.

There seems to be a export limit of 1000 issues, so for
projects with more issues you need to be creative :-) (left
as an exercise to the reader).

Tim


_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Reply | Threaded
Open this post in threaded view
|

Re: JIRA migration to bugzilla

Federico Leva (Nemo)
Terrible newlines/escaping again as with the sourceforge import (is
there an open bug for this?), but great! I assume you're also importing
closed bugs?
Can the TS admins please follow the procedure for the TS-related JIRA
projects so that he can import them when JIRA approaches closure/is set
read-only? Thanks.

Nemo

_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Reply | Threaded
Open this post in threaded view
|

Re: JIRA migration to bugzilla

Merlijn van Deen
Hi Nemo,

On 23 December 2013 13:12, Federico Leva (Nemo) <[hidden email]> wrote:
Terrible newlines/escaping again as with the sourceforge import (is there an open bug for this?),
This is now fixed -- the default jira REST format does not include newlines. I'm now using the HTML format, which is converted back to markdown-ish plain text.
 
but great! I assume you're also importing closed bugs?
Currently, only bugs with status status in (Open, "In Progress", Reopened, "In Review", Assigned, "Waiting for customer") are converted; If you think it's useful, I can also convert the closed bugs, and also close them on Bugzilla. Doing a full status-status mapping is not on my to-do-list.


If you want to test on a local bugzilla: I downloaded a VM from http://www.turnkeylinux.org/bugzilla ; I had to run /var/www/bugzilla/install-module.pl to get the xml-rpc api working.

Merlijn

_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Reply | Threaded
Open this post in threaded view
|

Re: JIRA migration to bugzilla

Silke Meyer
In reply to this post by Merlijn van Deen
Hi Merlijn, hi Tim,

how cool! Thanks for your work! I saw that Tim went through a whole
lot of tickets in Jira. I poked Nosy, DaB. and Mette, if one of them
could react upon the open ssh key requests. However, I don't know how
often they are online these days. Please understand if it takes a
moment.

Best, Silke

2013/12/21 Merlijn van Deen <[hidden email]>:

> Hello all,
>
> Today, I hacked together a JIRA migration tool. If you want your bugs
> migrated please do the following two things:
>
> 1) Under Administration, <your project>, People, add 'Bugzilla Bug Exporter
> (valhallasw)' to 'Administrators' and click 'Update'. Otherwise, the bot
> cannot close the bug.
>
> 2) File a bug in bugzilla using the following link:
> https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia&component=Bugzilla&cc=valhallasw@...,marc@...&blocked=58821&comment=Which%20JIRA%20project%20do%20you%20want%20to%20convert%3F%20(link)%0A%0AWhich%20component%20name%20(under%20%27Tool%20Labs%20Tools%27)%20do%20you%20want%3F%0A%0ADid%20you%20add%20%27Bugzilla%20Bot%20Importer%20(valhallasw)%27%20to%20the%20administrators%20in%20your%20JIRA%20project%3F
>
> 3) Your bugs will be migrated for you! See
> https://bugzilla.wikimedia.org/58820 for an example of what the converted
> bug looks like.
>
> Merlijn
>
> _______________________________________________
> Toolserver-l mailing list ([hidden email])
> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
> Posting guidelines for this list:
> https://wiki.toolserver.org/view/Mailing_list_etiquette



--
Silke Meyer
Internes IT-Management und Projektmanagement Toolserver

Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 260

http://wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Reply | Threaded
Open this post in threaded view
|

Re: JIRA migration to bugzilla

Merlijn van Deen
In reply to this post by Merlijn van Deen
On 23 December 2013 13:55, Merlijn van Deen <[hidden email]> wrote:
Currently, only bugs with status status in (Open, "In Progress", Reopened, "In Review", Assigned, "Waiting for customer") are converted; If you think it's useful, I can also convert the closed bugs, and also close them on Bugzilla. Doing a full status-status mapping is not on my to-do-list.


Guess what? I found some time to implement it. Closed bugs are now also imported (without assigning the bug to the original assignee, or adding CC's, to limit the bug spam). Statuses and resolutions are also converted. 


Merlijn

_______________________________________________
Toolserver-l mailing list ([hidden email])
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette