Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E044B200B73 for ; Mon, 29 Aug 2016 17:15:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DED22160AB8; Mon, 29 Aug 2016 15:15:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2EE34160A89 for ; Mon, 29 Aug 2016 17:15:39 +0200 (CEST) Received: (qmail 30288 invoked by uid 500); 29 Aug 2016 15:15:38 -0000 Mailing-List: contact dev-help@allura.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@allura.apache.org Delivered-To: mailing list dev@allura.apache.org Received: (qmail 30273 invoked by uid 99); 29 Aug 2016 15:15:38 -0000 Received: from allura-vm.apache.org (HELO allura-vm) (140.211.11.147) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Aug 2016 15:15:38 +0000 Received: from allura-vm.apache.org (localhost [127.0.0.1]) by allura-vm (Postfix) with ESMTPS id E780D2802C9 for ; Mon, 29 Aug 2016 15:15:37 +0000 (UTC) Content-Type: multipart/related; boundary="===============5962391403640065797==" MIME-Version: 1.0 To: dev@allura.apache.org From: "Dave Brondsema" Reply-To: "[allura:tickets] " <8122@tickets.allura.p.forge-allura.apache.org> Subject: [allura:tickets] #8122 Add a ForgeImporter for JIRA Tickets Message-ID:

Sender: tickets@allura.p.forge-allura.apache.org In-Reply-To: <57c43c6e6d19cd7760d99f7c.tickets@allura.p.forge-allura.apache.org> References: <57c43c6e6d19cd7760d99f7c.tickets@allura.p.forge-allura.apache.org> Date: Mon, 29 Aug 2016 15:15:37 +0000 (UTC) archived-at: Mon, 29 Aug 2016 15:15:40 -0000 --===============5962391403640065797== Content-Type: multipart/alternative; boundary="===============0553408703041867830==" MIME-Version: 1.0 --===============0553408703041867830== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit JIRA also has a REST API which is another way data could be loaded in. https://docs.atlassian.com/jira/REST/cloud/ I wonder if the formats are similar and we could support both, or if we'll need to pick just one. The backup export seems like you might have to be an Admin to use it, which might not work for everyone. The REST API requires direct access to the server and login credentials for it, which wouldn't work if the server is behind a firewall, or simply people don't want to share their credentials. I also see an "export" link with many options, when looking at a list of tickets, e.g. on upper right of https://issues.apache.org/jira/issues/?jql=text%20~%20%22allura%22%20and%20labels%20%3D%20gsoc2016 Anyone can use that, plus you can do it for just certain tickets if you only want to migrate some tickets. Maybe that is a good option? --- ** [tickets:#8122] Add a ForgeImporter for JIRA Tickets** **Status:** in-progress **Milestone:** unreleased **Created:** Mon Aug 29, 2016 01:45 PM UTC by Rohan Verma **Last Updated:** Mon Aug 29, 2016 01:45 PM UTC **Owner:** Rohan Verma As discussed previously, adding an importer for issues hosted on JIRA would ease convincing projects to use Allura. JIRA provides a method to backup issues. https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html The backup includes the following data: * Issues * Users and their group settings * Avatars * Attachments if selected In XML format. We already have an importer for GitHub, and the code /ForgeImporters/forgeimporters/github/tracker.py for it's ticket importer can be used for reference. I have started working on this and with the merge of this with the codebase I think would be a good time to approach Apache projects in the Incubator. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============0553408703041867830== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

JIRA also has a REST API which is another way data could be loaded in. https://docs.atlassian.com/jira/REST/cloud/ I wonder if the formats are similar and we could support both, or if we'll need to pick just one.

The backup export seems like you might have to be an Admin to use it, which might not work for everyone. The REST API requires direct access to the server and login credentials for it, which wouldn't work if the server is behind a firewall, or simply people don't want to share their credentials.

I also see an "export" link with many options, when looking at a list of tickets, e.g. on upper right of https://issues.apache.org/jira/issues/?jql=text%20~%20%22allura%22%20and%20labels%20%3D%20gsoc2016 Anyone can use that, plus you can do it for just certain tickets if you only want to migrate some tickets. Maybe that is a good option?

[tickets:#8122] Add a ForgeImporter for JIRA Tickets

Status: in-progress
Milestone: unreleased
Created: Mon Aug 29, 2016 01:45 PM UTC by Rohan Verma
Last Updated: Mon Aug 29, 2016 01:45 PM UTC
Owner: Rohan Verma

As discussed previously, adding an importer for issues hosted on JIRA would ease convincing projects to use Allura.

JIRA provides a method to backup issues.

https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html

The backup includes the following data:
Issues
 Users and their group settings
Avatars
 Attachments if selected

In XML format.

We already have an importer for GitHub, and the code /ForgeImporters/forgeimporters/github/tracker.py for it's ticket importer can be used for reference.

I have started working on this and with the merge of this with the codebase I think would be a good time to approach Apache projects in the Incubator.

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============0553408703041867830==-- --===============5962391403640065797==--