Edgewall Software
Modify

Opened 15 years ago

Last modified 5 years ago

#1505 new enhancement

Search all projects at once

Reported by: anonymous Owned by:
Priority: normal Milestone: topic-multiproject
Component: search system Version: 0.8.1
Severity: major Keywords: global search multi project
Cc: trac.tickets@… Branch:
Release Notes:
API Changes:

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 (0)

Change History (8)

comment:1 by anonymous, 15 years ago

Keywords: multi project added

comment:2 by anonymous, 15 years ago

Cc: trac_tickets@… added

comment:3 by anonymous, 14 years ago

Cc: trac.tickets@… added; trac_tickets@… removed

comment:4 by Christian Boos, 13 years ago

Milestone: 1.0
Owner: changed from Jonas Borgström to Christian Boos
Severity: normalmajor

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).

comment:5 by Christian Boos, 10 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:6 by Christian Boos, 9 years ago

Milestone: triaging0.13

Related to #130, this ticket focuses on the request handling (i.e. the TracDev/Proposals/MultipleProject#URLspacefordifferentprojects part).

comment:7 by Christian Boos, 9 years ago

Milestone: 0.130.14-multiproject

comment:8 by Ryan J Ollos, 5 years ago

Owner: Christian Boos removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.