incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] Re: #6535 Ticket import for github
Date Fri, 30 Aug 2013 14:17:17 GMT
For the events feed, there are several types of events that can occur.
  I think we should handle "closed" "reopened" and "assigned" and ignore the others.


** [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
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 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