Page MenuHomePhabricator

Provide upgrade path for jira users
Closed, ResolvedPublic

Description

Currently, no clear upgrade path from jira to bugzilla exists (except 'copy-paste all bugs'). Converting bugs should be possible; the BZ end already exists (although somewhat buggy) as https://github.com/wikimedia/pywikibot-sf-export

JIRA provides a REST API:

https://jira.toolserver.org/rest/api/latest/issue/ACCAPP-684

see https://docs.atlassian.com/jira/REST/latest/ for docs


Version: unspecified
Severity: normal

Details

Reference
bz58794

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:15 AM
bzimport added a project: Toolforge.
bzimport set Reference to bz58794.

I hacked together a working conversion bot today. See for example

https://jira.toolserver.org/browse/PYWP-2

and

https://bugzilla.wikimedia.org/58820

The bots needs closing rights on the project on JIRA - the easiest is to add 'Bugzilla Bot Exporter (valhallasw)' to the admin group on https://jira.toolserver.org/plugins/servlet/project-config/<PROJECT KEY>/people

On the BZ end, the bot can set the assigned user, but currently does not have the rights to do this.

The bot only supports a single product/component/version, BUT takes JQL queries as input. If multiple products/compontnts/versions are required, this can be done by filtering the jira end using JQL and running the bot multiple times.

Process, as sent to toolserver-l:

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.
  1. File a bug in bugzilla using the following link: https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia&component=Bugzilla&cc=valhallasw@arctus.nl,marc@uberbox.org&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
  1. Your bugs will be migrated for you! See https://bugzilla.wikimedia.org/58820 for an example of what the converted bug looks like.

I would have hoped for a "nicer" result (i. e. that the bug looks as if it has always been in Bugzilla, with usernames & Co.), but - wow! :-) Thanks.

It's technically possible, but it requires command-line access to the bugzilla server. Andre mentioned he preferred this solution (as it's not clear what the security/stability implications are of imports via the command line).

I have improved on two things now:

  • a different message format; instead of using the 'reply' format, use something more like a 'forward' format, i.e.

From: Merlijn van Deen <....>

Date: Wed, Jan 1 2013, etc

Message...

  • linebreaks etc. are now converted. JIRA only hands a plain text version without any newlines by default. I now parse the html version of messages back to text.

(In reply to comment #4)

It's technically possible, but it requires command-line access to the
bugzilla
server. [...]

There would also be the problem of JIRA functionality missing their counterparts in Bugzilla, e. g. resolutions "Answered", "Declined", etc., so definitely not trivial.

(In reply to comment #2)

Today, I hacked together a JIRA migration tool.

Whou. Congrats, seriously!