infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16128) Migrate JIRA to Github Issue
Date Fri, 02 Mar 2018 02:21:00 GMT

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

Chris Lambertus commented on INFRA-16128:
-----------------------------------------

Sorry, we will not help you migrate to a third party we do not control nor have the tools
for.

Once we change your Jira to read-only, it is read-only. This affects all existing issues.



> Migrate JIRA to Github Issue
> ----------------------------
>
>                 Key: INFRA-16128
>                 URL: https://issues.apache.org/jira/browse/INFRA-16128
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Github, JIRA
>            Reporter: yukon
>            Priority: Major
>
> Hi,
> Please help us migrate JIRA to Github issue, and we have reached a lazy consensus in
RocketMQ community, below is the discussion thread:
> https://lists.apache.org/thread.html/247ea9a9f1247747644278cb0050180541a859a592184bc27ab531d2@%3Cprivate.rocketmq.apache.org%3E
> And consider that we have many ongoing issues like GSoC projects, we want to keep the
JIRA system read-only for a period of time that means we couldn't open new tickets but the
old tickets are operational, is that possible?



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

Mime
View raw message