I am fine either way, so I guess I'd say go ahead and merge it. Since its using the `__json__` method it is already using just public fields. So only problem in the future would be if there's a new field that is really big and we don't want in the list result. Which wouldn't be too big of a problem.
--- ** [tickets:#7789] Return more fields in ticket API search results** **Status:** review **Milestone:** unreleased **Labels:** allura-api sf-1 sf-current 42cc **Created:** Thu Oct 30, 2014 09:56 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 12, 2014 04:10 PM UTC **Owner:** Igor Bondarenko On ticket search API results, only the "summary" and "ticket_num" fields are present. We should include many more, if not all fields that solr has available. That will allow API clients to get information in a single request instead of fetching every individual ticket to get whatever data is needed. --- 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.
