Using timeline as the trac homepage

ticket.query solution

Using the following criteria to find out modified tickets in last 30/14 days:

changetime=03/30/2013..04/18/2013&max=0

the api ticket.query will return a list of ticket id. We will get details change log for each ticket, using the multicall proxy. The list the changes by date: today, yesterday, etc. just like the timeline page on Trac project.

• we could search week by week.

Here are the possible solution:

• using ticket.query to search by a time range. this will return a list of ticket ids.
• multicall to get all tickets details, We need ticket title and created time and reportor for a new ticket. A brand new ticket doesn't have any change log.
• multicall to get all changelogs for all tickets.
• Work through chagne logs one by one for which is younger than the from time.
• each changelog will become one line on the timeline page.
• each line will provide the following information:
  • id
  • ticket title: the summary field.
  • author: reporter or owner or comment author
  • action: the action will mainly based on the new status of the ticket: created, accepted, assigned, reopened, closed, or updated. If ticket status is not change, action will be updated.
  • summary: will tell status change, comments excerpt, or excerpt of ticket description.

Starting

Some thoughts

• There is NO xmlrpc api for timeline at this moment.
• There are some patch for XMLRPC plugin to shou the timeline, But is too old and no update for years. https://bitbucket.org/mathieuravaux/trac-xmlrpc-plugin-additions
• TracXMLRPC plugin provides a api to get recent changed ticket by a timestamp: ticket.getRecentChanges(datetime since). Which will return a list of ticket IDs.
• Once we get the IDs, will find the details activities for each ticket.
• Details activities includes: comments, resolutions, author, etc.
• We should use WP_List_Table to show the activities.

How about using Solr search engine?

• real time index to Solr instance.
• extra fields for change log: timestamp, author, etc.
• then time line will be Solr result.
• has to be one solr doc for each change?!