Version 12, last updated by Assembla Support at 23 Feb 16:00 UTC

Steps to perform

Create a Trac/SVN space on Assembla

Import your Trac dump

  • Go to the Subversion & Trac tab, then click the link admin
  • If you are not logged in on trac will see this:

    so please, Login
  • When you logged in, you will see admin panel

    click to Data import/Export
  • Import your trac env (zip) file

Convert Trac tickets to Assembla Tickets

  • Click the link Assembla Project Page near the top left
  • Click the Subversion & Trac tab, then click the button “Import Trac tickets to Assembla Tickets”
  • Confirm that the Trac tickets were imported to the Assembla Tickets tool

Remove Trac tool and add SVN/Source tool

  • Click the Admin tab, then click the Tools link
  • Remove the Trac/SVN tool (make sure to export the SVN repository first if needed)
  • Add the Source/SVN tool
  • Go to the Source SVN tab and click the Import/Export subtab
  • Import your SVN dump

Notes if your SVN dump is from an SVN system other than Assembla:

Users can fix authors in their dump to match their usernames in Assembla before importing the SVN dump:

  • Download dump
  • install svndumptool
  • Get list of all commit authors from dump: svndumptool.py log exampleSvnDump | awk '/^r/ {print $3}'
  • Check if any of given author names have existing username in assembla and is not member of the space we intend to upload dump to.
  • Make a list of conflicting user names, i.e. author names that already exist on assembla and are not related to the space the dump is going to be uploaded
  • Ask users to fix the dump and re-upload. Users can use following tool to change author name: svndumptool transform-revprop svn:author old_name new_name current_repo.dump new_repo.dump

Notes if your Trac dump is from a Trac system other than Assembla

Just import as described in Import your Trac dump

Additional notes

  • Ticket numbers will remain as was in trac.
  • Ticket attachments will remain the same.
  • References to tickets in code commits will remain if they use our conventions:
    • Use Closes #4 to close ticket 4. “closed”, “close”, “fix”, “fixed”, and “fixes” will also close a ticket.
    • “Re #4”, “references”, “refs” and “see” will add a comment to the target ticket.
    • “test #4” will mark the ticket to “Ready to Test” and add the comment to the ticket.
  • References to revisions in tickets will remain as it was in trac (should be fixed soon)