|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Jeff Turner [Atlassian] - 10/Dec/03 04:57 AM
It would be nice. The problem is that many fields (versions, components, custom fields) are project-specific. How could a cross-project search also specify these fields? Just ignore them, or list each (projectA's versions, projectB's versions, ...).
This is an important feature for us.
It would be fine to ignore any custom fields that don't apply across the category. This seems consistent with the current approach for project & issue type searching (ie: limit the parameters to those which apply to the particular combination chosen). Implementing this would dramatically reduce the need for I think searching for issues by category could be done quite nicely with a custom field that only has a "search" template.
I agree with Martin, this is a very important feature for us as well. It would definitely be acceptable to limit the list of custom fields and issue types to those that exist in all the projects in the category. In a perfect world, categories wouldn't exist and we'd have nested projects instead (with inheritance of custom fields and so on) but with what we have now I think Martin's suggestion is the most feasible.
This is also important for us. We have many projects, and we're having to trim down the list and merge some because of the lack of this type of functionality. Also see JRA-6825.
This is related to JRA-2837, if the projects view was sorted by project category, and the category names could be selected then this would be a good start.
This shouldn't be too hard, you could just ensure that selecting the category name activated a javascript that selected all the projects in that category, or somthing similar. Now that
Hi,
You are right, now that multi-project searching is implemented, this feature is easier to do. Unfortunately, at the moment we cannot provide a date for the implementation of this feature. For more information on how the features are scheduled please refer to: Thanks, Just to add to my comment:
Plase note that we do consider this fetaure to be important and useful. We are keeping it in mind. Thanks, Something else to consider when implementing this feature. Some users have expressed an interest in being able to set an overriding category filter - once set, all searches that user does would only display results for projects in the category. This would need to be per user, and preferably persist between sessions.
This will be particularly useful where Jira is used to manage several discrete programmes of work, each with their own projects, and would reduce the need for multiple instances of Jira. I have many filters that I have to update as I add projects to the system. Most of these updates would be eliminated if I simply could search by category. This would be very helpful to us overall.
We have three departments using Jira each with dozens of projects. This feature would significantly simply our queries. This seems so simple to add especially now that you have the plugin architecture available. We can search for global custom fields easily. How is this any more complex? Can we please get this in a near future version?
Bob,
Sorry for the late reply, its quite busy around here. You are right, the functionality is not very complex from technical perspective, the only issue is time and resources that we have available, which are quite limited at the moment. At the moment I am unable to provide an accurate date for implementation of this feature, but having said that we can see if this is a 'low hanging fruit' that we can solve in one of the upcoming JIRA versions. Anton Being able to restrict a search ( and filters ) by project category would be BIG improvement, without it project categories aren't very useful for organising projects into logical groups, as you can't set up filters and all the goodness that follows - dashboards, feeds etc for those categories.
I have the exact same issue.
I have multiple clients using JIRA all assigned to their own project under a "Support..." group. When a new client is added, I add a new project for him. I tried coming up with a default dashboard for all of them, but I had to use a list with only these project selected. This means that everytime I had a new client I also have to update the list to include the client's project in it. Unless there is an easier way to accomplish this. Where can I find information on how people using JIRA for their clients have configured their application? A kinda of "How to Guide" or "Tips"... I assume that a lot of JIRA's user are using to log issues logged by their clients. Thanks [ Show » ] Pascal Laplante [19/May/06 08:13 AM] I have the exact same issue. I have multiple clients using JIRA all assigned to their own project under a "Support..." group. When a new client is added, I add a new project for him. I tried coming up with a default dashboard for all of them, but I had to use a list with only these project selected. This means that everytime I had a new client I also have to update the list to include the client's project in it. Unless there is an easier way to accomplish this. Where can I find information on how people using JIRA for their clients have configured their application? A kinda of "How to Guide" or "Tips"... I assume that a lot of JIRA's user are using to log issues logged by their clients. Thanks There are 22 votes for JRA-2837, 32 votes for JRA-3464, 1 vote for JRA-6825 should make it one of the more requested features. Considering Atlassian doesn't even have this assigned to a future version, I wouldn't expect this anytime soon. It is amazing to me that they can't seem to find time to add this basic functionality that should only take a few hours. Obviously making Jira work in new markets (Japan) is more important then adding the functionality that should have been there from the beginning.
I newly added
Anyway, eagerly waiting its implementation... Kamil Eagerly still waiting... Could someone at Atlassian give us some indication where this highly needed feature that should be able to be easily accomplished could be added?
Bob,
I hope to blog about JIRA's direction for the next 6 months in the coming weeks, as we near the 3.7 release. I'll make sure that this email goes to the mailing list. Cheers, We have got several departments using Jira - and also a lot of filters of course.
Every head of any department is allowed to see each others projects. When you have got filters for your own department you always have to adopt each filter whenever a new project is created because now you can just limit the filter to several projects or assignees but not project categories which are now used for the different departments. With the option to filter per category errors could be prevented! Gerald Has anyone implemented in Jira Chris Wood's suggestion using Java Script: http://jira.atlassian.com/browse/JRA-2837#action_37479?
Essentially, we really need also the ability to search projects by categories. Based on the category selected, the appropriate project list will be presented. Hi all, we are using Jira Enterprise for managing a large number of project. We are also very eager to get filtering on Project Categories, as it would simplify our work significantly. I have voted for this issue.
Kind regards, Niklas Hagen, Mogul This is an interesting topic. I commented on JRA-3464 and suggested adding label on projects, and I think the same concept could be extended to versions and components. Then a few filter fields (Category Label, Project Label, Version Label, etc.) could be added that would allow for searches on the specific subset of projects/versions/etc..
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Search for issues in category
