allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohan Verma" <rohanverma2...@gmail.com>
Subject [allura:tickets] #8122 Add a ForgeImporter for JIRA Tickets
Date Mon, 29 Aug 2016 13:45:20 GMT



---

** [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.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message