I suggest you ...

Add Import/Export Functionality for Projects

The title says it all. Basically, the ability to import and export entire projects (repo, issues, wikis, walls, snippets, and the kitchen sink). GitLab stores so much more than just files and commit data, but there's no easy way to migrate this data between instances of GitLab.

384 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    crazyscience (Brandon)crazyscience (Brandon) shared this idea  ·   ·  Admin →

    31 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Nicolas GuilbertNicolas Guilbert commented  · 

        For anyone just looking for a csv-dump of the ticket list, this should be of interest:

        https://gitlab.com/raisoman/gitlab-sandbox/

        It's a plain html+js file producing an html table of all the tickets in the repository indicated via a query parameter. The html table can then be copy-pasted (Ctrl+A Ctrl+C) into a spreadsheet.

        At the time of writing the fields "created_at", "iid", "title", "state", "labels", "updated_at" are exported.

      • Colan SchwartzColan Schwartz commented  · 

        @MeXx: Any reason why that's hosted on GitHub and not GitLab.com? ;)

      • Anonymous commented  · 

        Please support csv to import into Jira, and json wouldn't hurt either.

      • robduyserrobduyser commented  · 

        detailed csv export of all (open and closed) issues, would be really great... have tried using the rss feed, but this is not sufficient

      • AnandaAnanda commented  · 

        How can i import gitlab issues? Is the new feature ready yet?

      • Anonymous commented  · 

        "storing them in git is not an option" - well, why not?

        Like the wiki has a separate repository, there could be a project.archive.git repository that contains a clone of the project git, the wiki, SQL dumps and other exported resources.

      • simonzacksimonzack commented  · 

        Be sure to export and import all timestamps too! A lot of projects don't handle this or don't handle this properly.

      • DougDoug commented  · 

        +1 - Haven't gotten any pull requests for this yet?

      • BjørnBjørn commented  · 

        +1. Export issues with comments++ to CSV or JSON or whatever portable format other tools and services accepts!

      • tuxayotuxayo commented  · 

        It would be awesome to migrate data between different instances, then you would be able to say "Stay because you can leave"

      • Deedee OlsenDeedee Olsen commented  · 

        As a Tech Project Manager, I'm trying to use this system for bug tracking to make it easier on my developers, but not being able to export the full list into Excel for reporting or anything is just a bit of a headache. I'm not going to be able to get an executive to look in Git to get a picture of where we're at so exporting it into Excel would be awesome.

      ← Previous 1

      Feedback and Knowledge Base