I just tried the export button on the issues page. And it gives the issues in XML format but I guess it is limited to 100, maybe there would be a way to paginate through all the issues. When clicking on the JSON format, it says that we require admin access.
Anyways, since XML is a format that seems to be widely supported by JIRA when we export; I'm going to try parse it and save it into Allura. We can explore into what would be the best way to approach bulk importing. The backup option seems to be the easiest but as you pointed out, would only be available to an admin user. Export link seems to work, and would require automating the process using a user account. --- ** [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 03:15 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.
