allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #8122 Add a ForgeImporter for JIRA Tickets
Date Mon, 29 Aug 2016 15:15:37 GMT
JIRA also has a REST API which is another way data could be loaded in.
 I wonder if the formats are similar and we could support both, or if we'll need to pick just

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
 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.

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/
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 because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message