Actually this would probably be best as a separate tool so it doesn't clutter the `ForgeTracker` code.
SourceForge will probably make a simple implementation for internal use, and can look at open sourcing it in the future. --- ** [tickets:#7790] Basic support for searching tickets across separate forges** **Status:** open **Milestone:** unreleased **Created:** Thu Oct 30, 2014 10:03 PM UTC by Dave Brondsema **Last Updated:** Thu Oct 30, 2014 10:03 PM UTC **Owner:** nobody After [#7789] is done, we should add a mechanism to allow a "federated" ticket search that searches the current app, but also uses a remote URL to conduct a search and return the results. For now lets keep it really simple and just have the ticket search controlle take an extra URL param which is a REST URL for another tracker. Nice UI, saved configs, etc we can think about later. Then the controller an do a local search and a remote search with the same query, and combine the results. The template would show them together and the external tickets would link over to the external site. Those should be marked somehow; looks like we have the classic "external link" icon in our icon image (not sure if its got a CSS class yet). --- Sent from forge-allura.apache.org because [email protected] 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.
