You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Thomas Fischer (JIRA)" <ji...@apache.org> on 2006/05/25 17:35:30 UTC
[jira] Updated: (INFRA-761) Import Torque issues into JIRA
[ http://issues.apache.org/jira/browse/INFRA-761?page=all ]
Thomas Fischer updated INFRA-761:
---------------------------------
Attachment: torque-source.tsv
Attached the TSV file for the Torque Source issues from Scarab. I did the following:
- Search all issues from the module Torque-Source inScarab
- Exported them as TSV
- removed the enclosing html
- replaced >, < and & by <,> and &
- manually removed the issues which are already migrated manually.
Unfortunately, comments and attachments are not included in the TSV. but in the few cases where they are still wanted one can transfer them manually from scarab.
> Import Torque issues into JIRA
> ------------------------------
>
> Key: INFRA-761
> URL: http://issues.apache.org/jira/browse/INFRA-761
> Project: Infrastructure
> Type: Task
> Security: public(Regular issues)
> Components: JIRA, Scarab
> Reporter: Jeff Turner
> Assignee: Jeff Turner
> Attachments: torque-source.tsv
>
> Torque has a few hundred issues in Scarab, and since Scarab can export these as tab-separated values, we can import them into JIRA. Or at least we can once a) we've upgraded to the upcoming 3.5.4 (INFRA-737) which would include a bugfix for handling TSVs (http://jira.atlassian.com/browse/JRA-9653).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira