You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Jeff Turner (JIRA)" <ji...@apache.org> on 2006/07/01 11:56:30 UTC

[jira] Commented: (INFRA-761) Import Torque issues into JIRA

    [ http://issues.apache.org/jira/browse/INFRA-761?page=comments#action_12418790 ] 

Jeff Turner commented on INFRA-761:
-----------------------------------

This job is waiting on an upgrade to 3.6.x (for the TSV parsing bug mentioned in the summary). I'm halfway through the upgrade procedure (taking a while as I'm documenting it this time) and will test the TSV import when I've got 3.6 upgraded locally.

> 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-documentation.tsv, 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