|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Erik S - 05/Jan/06 05:43 PM
I'd like this feature also, but would prefer that the user only be presented the categories of the projects he has permission to browse.
We have a couple of hundred projects, so project categories are essential for us or the project selection becomes tedious.
We'd also like to pull off some cross-project searches which may span project categories, but this is still not clear. For instance we'd like to connect software issues to hardware installations and then check for hardware related problems across projects. But this is turn means we'd like to build up an inventory of hardware installations for which there is no support in Jira. Any way , this feature coul'd give us the capability of having some dynamic filters .. i mean if i have a filter on a category , each project added to this category must be selected by the filter ..
We have a similar need to be able to dynamically include new projects in multiple filters. Using project categories is probably a good solution for this particular problem.
However, I'd like to raise the idea of using label on projects. This would address the same issue (simply label the new project with the category name), as well as provide the ability to target a subset of large project categories. Example: Project Category = System 1
Project Category = System 2
It is then possible to create filters, and dynamically add projects to those filter, that search across the entire category or across a specific set of projects (within the category or across categories). I like Yair's idea. This would certainly enhance our filtering ability.
We also need this feature. Without I will have to remember to update all my saved filters each time a project it added (which happens regularly)
After talking to our CM guys I have identified a few different needs:
1) Be able to search for issues across multiple projects, for instance by labelling projects. Categories are insufficient, the same Jira project gets reused many times across many real world projects. Project labels would help. 2) To define baselines. Given a number of projects, for each project indicate one version which is part of the baseline. This makes it possible to determine exactly what version of what piece of software got delivered to a particular customer. Obviously you need to be able to look at the issues associated with a baseline, across the projects which are included in the baseline. One baseline refers to many projects. For each project, the baseline points to a version.
Baselines are more useful than project labels, but are more difficult to grasp. With baselines I don't think you would need project labels. The next step is assets, being able to create a "customer" or "installation" in the system and linking it to a baseline so you can see what software versions are actually out there. Then if you find a problem in a module, you can backtrack to see which installations are affected... Back to the initial request: "allow filtering by project category".
I know by heart Atlassian policy to chose which feature to implemente (cf Votes, etc.). Anyway I cannot understand why such an easy feature (should not take more than 2 hours to implemente) with such a big added value, and yet so many votes, cannot be implemented right now. (besides, lots of issues with more votes are not implemented due to their complexity ...) So, thank you Atlassian for implementing this one. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
allow filtering by project category
