Migrating from Flyspray to Jira

I want to check and make sure the team agrees with my plan of action on opening up Jira and closing down Flyspray.

There are currently 280 open issues in Flyspray and I intend to shut down Flyspray today by removing everyone’s privileges. However, it would take a few days of work to export the data from Flyspray for import into Jira, and I am going to ask (publicly) instead that anyone with open issues that are still relevant in Flyspray to sign-up on Jira and create a new ticket for it, and reference the original task from Flyspray in the description, either by URL or using the FS#123 approach.

Does anyone have any issue with doing this? I know it’s bound to aggravate a few users who have been diligent with Flyspray, but the added benefits of our new issue tracking tool I believe outweighs the inconvenience.

Agreed No issues from my end with this approach.

I’ll be glad to do mine, but I worry that some genuine bugs will be lost becuase they were reported by people who are no longer active.

Could we delete them (or mark them inactive) or something when we move them to Jira? Then you could look over the remaining ones to see if any important ones still need moving.

Bob

They won’t be lost; they will still be available from the flyspray URL’s. I don’t want to break all the links in the forums and elsewhere, or make that information inaccessible. I just don’t have time to move them all myself by hand, and the import process is more than I have to take on as well.

And feel free to help move active issues over at will...

Sounds like a job for xPDO to me
Is there a staging or test version of Jira anywhere?
I’d love to see the db structure of these 2 apps to see if it’s even sane to consider. Oh, are they even on MySQL?

I could spend 3 or 4 days of my life trying to migrate this data without the users that submitted them, but I don’t want to. I want people to create new tickets in Jira only if there are actual bugs or feature requests that are still relevant and not resolved.

And no, no test versions of Jira. It’s hard enough to setup. Jira has a great import tool. That is not the issue.

Quote from: BobRay at Feb 26, 2008, 01:06 AM

Could we delete them (or mark them inactive) or something when we move them to Jira? Then you could look over the remaining ones to see if any important ones still need moving.

How about creating a "Task Type" or "Category" called "Ported to Jira" or something so that we can flag and then filter the tasks in FS to see if there’s anything important we’re missing?

How about just include FS#xxx in the task summary. That should be sufficient to filter by, and give us proper links to both issues where necessary, no?

If there are issues of ours listed in Flyspray that have been fixed, should we still port them to Jira, or forget about them?

Bob

Quote from: BobRay at Feb 26, 2008, 02:21 PM

If there are issues of ours listed in Flyspray that have been fixed, should we still port them to Jira, or forget about them?

Let sleeping dogs lie, or so I always say...