Edgewall Software

Ticket #1505 (new enhancement)

Opened 4 years ago

Last modified 21 months ago

Search all projects at once

Reported by: anonymous Owned by: cboos
Priority: normal Milestone: 1.0
Component: search system Version: 0.8.1
Severity: major Keywords: global search multi project
Cc: trac.tickets@…

Description

In case of mulitple projects, it would be very interesting to have a global search (across all projects and their tickets). Is suppose this would be quite easy to accomplish, if this would call the search of each separate project and display the results in a single page ...

Attachments

Change History

Changed 4 years ago by anonymous

  • keywords multi project added

Changed 3 years ago by anonymous

  • cc trac_tickets@… added

Changed 3 years ago by anonymous

  • cc trac.tickets@… added; trac_tickets@… removed

Changed 21 months ago by cboos

  • owner changed from jonas to cboos
  • severity changed from normal to major
  • milestone set to 1.0

Definitely something that should be possible when multiple projects per environment gets implemented. This should be extended to the notions of global queries, global timeline as well.

One idea would even to be able to do that on sets of projects, so that single project or all projects would be the two extremes of a more general mechanism.

This could perhaps translate to some conventions regarding the URL mapping, if the project is the mandatory first element in the URL path:

  • /project1/search would do the search in project1 only,
  • /project1,project2/search would do the search in project1 and project2
  • /p*/search would do the search on all projects starting with "p"
  • /*/search would do the search on all projects
  • //search would require to interactively choose the projects to be included in the search (e.g. using a multiselect form field).

Implementation Note

This could be done by a preprocessing on the req.path_info, before the request dispatching itself, so that the existing match_request() methods wouldn't have to be modified. A list of matching projects names could be associated to the req (req.args['projects']). If the list is empty, then the reject could either be rejected when it can't be satisfied, or a project selector could be added to the form (e.g. for the search, as described above).

Add/Change #1505 (Search all projects at once)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from cboos. Next status will be 'new'
The owner will change from cboos to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.