infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16279) incubator-mxnet
Date Mon, 23 Apr 2018 10:24:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447911#comment-16447911
] 

Gavin commented on INFRA-16279:
-------------------------------

To clarify : In Github, you use labels. In Jira these get imported as 'Issue Types' or 'Components'
(not Jira labels.). 

So what Im trying to explain is, what the labels are in Github, are to help determine what
I can map them to in Jira. 

Example:-

Label 'Bug' in Github I would map to 'Issue Type - Bug' in Jira.
Label 'Question' I would map to 'Issue Type - Question' in Jira
Label 'Memory' I would map to a 'Component - Memory' in Jira.

etc 



> incubator-mxnet
> ---------------
>
>                 Key: INFRA-16279
>                 URL: https://issues.apache.org/jira/browse/INFRA-16279
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Chris Olivier
>            Assignee: Gavin
>            Priority: Major
>
> We are trying to move to JIRA from github.
> Please, need all github issues imported into out JIRA (MXNet).
> Is there a way to do this automatically periodically, as it won't be possible to stop
everyone from filing issues on github.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message