Redmine

We are using Redmine internally in our organization and the current search function is confusing for our users also. We are using Redmine for task management (e.g. no RCS and code development stuff) and we have built an hierarchy of projects based on the organizational structure. For example, CIO has three departements beneath him and when searching, by default he would like to search every "project" under him. As it now, he has to make too many clicks to get where he wants and on the other hand the default Redmine search method is not suitable for us at all. So if possible, please make it configurable (preferrably redmine-wide).

Actually there does exist this capability already. When searching from the initial search entry field (usually in the top right of the screen) you only have the choice of one project.

When you actually perform the initial search you are taken to the Redmine search page which gives you the option to search one of;

a) current project,
b) my projects, or
c) all projects.

So a nice to have feature change would be to place 'my projects' and 'all projects' in the initial project choice but not actually necessary.

A quick and dirty way to change this Redmine behaviour is to edit apps/controller/search_controller.rb and edit in class SearchController < ApplicationController the various statements (for example, if you want to change the default search scope to global, you should change the else statement from @project to nil).

projects_to_search =
      case params[:scope]
      when 'all'
        nil
      when 'my_projects'
        User.current.memberships.collect(&:project)
      when 'subprojects'
        @project ? (@project.self_and_descendants.active.all) : nil
      else
        #@project
        nil
      end

I very much agree that either searching all subprojects should be the default, or that the default should be configurable.

My solution was to update the search form via the site theme. You should create javascripts/theme.js with the following content:

function customSearch() {
    var node = document.getElementById("quick-search");
    node.innerHTML = 
        "<form actuion='/search' method='GET'>" +
        "<a href='/search'>Search:</a>" +
        "<input type=text name=q>" +
        "</form>";
};

if (window.jQuery) { 
  $(window).load(customSearch);
}

Other search options can be easily added via form fields.

+1

I need this function, too.

Can the default search be configurable for each project?

Go MAEDA wrote:

We see issues of subprojects by default in issues page (Default value of Setting.display_subprojects_issues is True). So including issues from subprojects in search results by default is very natural.

Oh, I didn't know that displaying subprojects issues on main projects is configurable (my bad). In this case, I think that it'll be better to rename the option in something like "Include subprojects issues on main projects issues and search by default" and make the patch to take into account the setting. In this way, it'll be consistent in both cases (with option enabled and disabled).

What do you think, Go MAEDA?

Thanks, I'll update the patch soon.