#4213 Import from trac into ticket tool
A script exists at scripts/trac_export.py to extract trac tickets, and can be imported with scripts/allura_import.py Jon Schewe describes the whole process at http://mail-archives.apache.org/mod_mbox/incubator-allura-users/201303.mbox/%3CCALpcnoxEG%3DNJ7UG1dfOKj%2BbEPMtybGNStXZPVjfHrLyLDz%3DXLA%40mail.gmail.com%3E
Improvements needed:
- stability / handle errors (and possibly some refactor/cleanup)
- fetch and upload attachments (add uploads to import API?)
- set up milestones and proper field types (add to API? or setup directly, first?)
- SourceForge: a ScriptTask for us to run it for projects, including the user mapping
See [#6139] for wiki import.
We should strongly consider making our ticket import format match our API format, so that a backup [#3154] can be restored directly. ... or do that later
Related
Tickets: #3154
Tickets: #4213
Tickets: #6139
Tickets: #6140
Tickets: #6441
Responded on the SF support ticket.
Originally by: nathancarter
Perfect---worked like a charm, all tickets imported! Thanks for all the help here guys!! Very happy about the transition!
Last edit: Anonymous 2015-11-29
Closed #347. All changes in
je/42cc_4213You can run script task like this:
$ allurapaste script /var/local/config/production.ini /var/local/allura/ForgeTracker/forgetracker/scripts/import_tracker.py -- --file_data <json file with exported data> -a <api key> -s <secret key> -p <project> -t <tool> -u <trac url>See [#6441] for follow-up work.
Related
Tickets:
#6441