__group__,ticket,summary,component,version,severity,owner,status,lastmodified,chgs_auths,_description,_reporter,_milestone
enhancement,12188,Suggest / autocomplete keywords in ticket properties,ticket system,,normal,,new,218 days,5 by 3,Similar to the requests for users (#7628) and milestones (comment:12:ticket:7628 / #1901) it would be a huge time saver to get suggestions and autocompletion for ''keywords'' that have been used before on other tickets.,anonymous,
enhancement,12156,Ticket query renderer extension point,query system,,normal,,new,438 days,17 by 4,"I propose adding a new extension point `ITicketQueryRenderer`.

{{{#!python
class ITicketQueryRenderer(Interface):
    """"""Extension point interface for components that add HTML renderers of
    ticket query results.""""""

    def get_ticket_query_formats(self):
        """"""Return a list of `(format, format_label)` tuples.""""""

    def render_ticket_query(self, context, query, query_string, tickets, format):
        """"""Render the ticket query in the specified format.""""""
}}}

The query page could then allow selecting one of the available implementations from a dropdown and display the query results in various different ways.

The existing tables view could become the default implementation. The existing progress bars from the roadmap could provide a second implementation. New third-party plugins could provide further alternate views like pie charts, burndown charts, Kanban boards etc.

The roadmap could perhaps also reuse these renderers to display the milestones in the various ways.

The TicketQuery plugin could also use these renderers, selected by the existing `format` parameter (which already allows `format=table` and `format=progress`).

(Third-party visualization plugins already exist of course, but this extension point would allow them to be instantly deeply integrated with both the ticket query system, and the roadmap, make them usable in any wiki content via macro for free.)

----
Further considerations:

Possibly the batch editing could be separated out.

The existing [wiki:TracDev/PluginDevelopment/ExtensionPoints/trac.ticket.roadmap.ITicketGroupStatsProvider ITicketGroupStatsProvider] extension point could perhaps eventually be deprecated and removed. In its current form it seems to enable only very limited possibilities, potentially also provided by this new extension point.
",Peter Suter,
enhancement,12100,last_visit should update each time the user logs in,general,,normal,,new,3039 days,1 by 1,"It has been discussed on multiple occasions, most recently in th:comment:5:ticket:12302, that `last_visit` is often not a very useful indicator of when the user has last visited Trac. The value is only updated when the session data is saved. Would it make sense to update the value when the user authenticates?: [browser:/tags/trac-1.1.5/trac/web/auth.py#L130]. That might at least get us one step closer to having a value that indicates how recently the user has been seen.",Ryan J Ollos,