|
|
|
> 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. 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
I believe this functionality will be available in 3.2 through the ability to combine results of different filters to make a new filter. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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