Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,377
Community Members
 
Community Events
177
Community Groups

How to import GitLab issues to Bitbucket

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

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.

for me its not even working

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events