www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Turner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-761) Import Torque issues into JIRA
Date Tue, 26 Sep 2006 14:11:54 GMT
    [ http://issues.apache.org/jira/browse/INFRA-761?page=comments#action_12437845 ] 
            
Jeff Turner commented on INFRA-761:
-----------------------------------

> Thanks a lot, Jeff !

Sorry it took so long. I was envisaging a much more painful process than it turned out to
be.

> In the meantime, does it hurt if I modify the issues in TORQUEOLD (i.e setting those
with Status closed to Resolution resolved, and resolving issues which are solved in the meantime)
?

Go ahead.

--Jeff

> Import Torque issues into JIRA
> ------------------------------
>
>                 Key: INFRA-761
>                 URL: http://issues.apache.org/jira/browse/INFRA-761
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: JIRA, Scarab
>            Reporter: Jeff Turner
>         Assigned To: 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

        

Mime
View raw message