History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-3934
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Geoff Krapf
Votes: 2
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
JIRA

Exclude project or filter groups of projects

Created: 16/Jun/04 04:55 PM   Updated: 18/Mar/05 01:44 AM
Component/s: Filtering & Indexing
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Geoff Krapf, Jeff Turner [Atlassian], Johann Cohen-Tanugi, Kevin James and Mark Chaimungkalanont [Atlassian]
Since last comment: 174 weeks, 2 days ago
Resolution Date: 18/Mar/05 01:44 AM
Labels:


 Description  « Hide
We would like to be able to search for issues within a subset of projects.

I can think of two ways of implementing this:
(1) Add the ability to search all but exclude certain projects, or to include only particular projects
(2) Group projects, and allow searching within groups of projects.

I realize you'd loose custom fields when looking across projects where some have the fields and some don't, but it's more important for us to be able to look for all issues in several projects. (maybe the custom fields that are common across selected projects could be displayed?)



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Johann Cohen-Tanugi - 24/Aug/04 01:06 PM
I have a similar problem: I want to generate an automated filter seletion that would show up in my confluence web page. I know how to do that, but for the fact that I cannot group it selecting subsets of projects. The only choice is all or one of them only: totally defeats the purpose of a summary across a category etc...

Please what is the stauts and plans about this very limiting feature: I dont see why I cant ask all unresolved bugs assigned to John Doe within the projects A,B, and C. If John Doe has no permission to C, he would not appear as an assignee, and that still works fine....

thanks,
Johann


Jeff Turner [Atlassian] - 25/Aug/04 12:38 AM
> Please what is the stauts and plans about this very limiting feature

We were just discussing this yesterday - apparently the search engine can handle cross-project searches. It is a question of how to handle per-project fields like versions, components and custom fields. We'll be considering how to solve this issue when planning for the next release.


Kevin James - 27/Jan/05 11:17 AM
This is probably the most limitiing issue we continuously run into in JIRA. We would love to be able to build up a list of Project/Version/Components to filter on. Perhaps in the filter page the user could choose a Project/Version/Component from three drop downs and then Add it to some Project list. Then the user might select another Project/Version/Component and Add that combination to the list and so on. Then the user could set the other fields to filter on and run the filter. This would allow us to drop our custom global field for bundling project together which is proving to NOT work well because users forget to keep this field in sync with the version.

I think this is duplicate of JRA-699? I'll close this issue so we can track it there.

I believe this functionality will be available in 3.2 through the ability to combine results of different filters to make a new filter.