You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Igor Bondarenko <je...@users.sf.net> on 2013/09/04 10:31:34 UTC

[allura:tickets] #6535 Ticket import for github

Created:

* \#423 [#6535] Ticket import for github fixes (2cp)
* \#424 [#6535] Ticket import for github: pull events and handle pagination (4cp)
* \#425 [#6535] Ticket import for github: import into existing project (2cp)


---

** [tickets:#6535] Ticket import for github**

**Status:** in-progress
**Labels:** github import 42cc 
**Created:** Wed Aug 07, 2013 10:05 PM UTC by Dave Brondsema
**Last Updated:** Fri Aug 30, 2013 02:14 PM UTC
**Owner:** nobody

Use the github api for issues http://developer.github.com/v3/issues/#list-issues-for-a-repository to import tickets into allura.  You can use ForgeImporter's GoogleCodeTrackerImporter (at time of writing, cj/6464 on the apache repo has the latest code for it) and TracTicketImporter as reference.

Import all the fields & values possible, including comments, events (e.g. status changes) and attachments.  See the Google Code and Trac importers for examples of setting up the custom fields as needed, and referencing the remote users (keep the tickets & comments as anonymous and add identification with link into the body).


---

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

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