The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to import GitLab issues to Bitbucket

Paul Merker
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 21, 2018

Hi,

I am trying to import my GitLab Issues list (given in .csv format) into my Bitbucket repository because we are moving to Bitbucket.

Based on this https://confluence.atlassian.com/bitbucket/issue-import-export-data-format-330796872.html , I've written a little python script to read in the csv with the GitLab issues and convert them to expected json format.

My question: Which fields are really required and what to name the resulting json file ? I have tried naming it db-2.0.json aswell as db-1.0.json. Afterwards i zipped the file and tried to upload it. The error message from Bitbucket:

No db found in archive.

 

 

Thank you,

Paul

 

 

P.S.: Somehow I could not find anything on the internet addressing this topic.

 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Paul Merker
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 21, 2018

UPDATE:

Although I received emails about Bitbucket failing to import my issues, a while later I got one about a successful import. So it seems (i don't know why or how) that Bitbucket imported my issues correctly. I have also confirmed that inside the repo where all my issues appear. When a new issue is created, the issue id continues from the last imported issue number.

 

UPDATE v2.0:

tldr: As it seems the file has to be called db-1.0.json instead of db-2.0.json

Now everything works fine.

Shruti Mendhe
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 31, 2021

for me its not even working

TAGS
AUG Leaders

Atlassian Community Events