Redmine

This would certainly be a handy feature. I just hit a situation now where I wanted to see open tickets for several projects combined. These projects aren't parent/sub-projects of each other, they're just several disparate projects I happen to be involved in.

Of course, I could filter for tickets assigned to me, but I wanted an overview of all the tickets in the target projects.

I would like to see a Project filter added to the issues page as well. It would be most useful on the global "View all issues" page.

1
Our team is running 40 small projects and almost all the team members are involved into all the projects (this is also applicable for the support teams).
This is definitely important for us to have the global "View all issues" report which could be filtered by project(s).

thank you for your effort.

Ewan Makepeace wrote:

No we are talking about the issues list when not focussed on a particular parent:

[...]

Indeed, the subproject-filter isn't available in the global (cross-project) issue list. However, in latest trunk you are at least able to group (and collapse through JS) the global issue list by project (see issue #2679). It's not the same as such a filter as Nanda describes, but it is at least something for the moment...

Though, this issue should not be considered as resolved as such since you are specifically requesting the filter in the global issue list I presume...

Kind regards,

Mischa.

First of - that looks super cool, and I can see great uses for what you have done.
However there is an architecture problem - the data is paged on the server and client side grouping can only work on the subset of issues sent from the server. In Indonesia where bandwidth is constrained my default view is to see only 5 issues at a time for example.
So - unless we can filter by project on the server, we wont get the issues we want in the browser and client side grouping (while nice) wont solve that problem.
Also a huge application for this is saved queries - I want to build and save queries for certain groups of projects. That requires there to be a field in the query builder for me to save (as was done with Sort order?)

Ewan Makepeace wrote:

First of - that looks super cool, and I can see great uses for what you have done.

You should thank Jean-Philippe (and maybe Andrew Chaika) for the issue grouping feature. I haven't done anything for it's implementation. I don't even have commit rights to the redmine svn-repo (don't deserve them either :)

Ewan Makepeace wrote:

However there is an architecture problem - the data is paged on the server and client side grouping can only work on the subset of issues sent from the server. In Indonesia where bandwidth is constrained my default view is to see only 5 issues at a time for example.
So - unless we can filter by project on the server, we wont get the issues we want in the browser and client side grouping (while nice) wont solve that problem.

This indeed makes clear to me why you need the sub(project) filter (instead of grouping) on the global (cross-project) issue list. Though one caveat (maybe even the reason why it's not implemented yet): currently the filter is actually a subproject-filter and since while on the global issue list there is no sub-project available since we not on a project issue list... :S

Ewan Makepeace wrote:

Also a huge application for this is saved queries - I want to build and save queries for certain groups of projects. That requires there to be a field in the query builder for me to save (as was done with Sort order?)

Indeed. But I guess that the filter becomes also available on the global custom query "builder" once the filter has been implemented on the global issue list filters as requested. Though imho that is not the same of the "Sort order" option in the custom query "builder"...

HTH!

Kind regards,

Mischa.

BIG +1 for what its worth

I would also like this. But in the meantime, similar functionality is available via this plugin: http://www.redmine.org/wiki/1/PluginGlobalFilter