|
To be honest, I didn't really understand your suggestion. But this is not a high priority need for us. I just wanted to be ready should the need arise.
Neal,
Nick is suggesting to use a custom field to group issues. You can use a select list custom field with 1 option for each "issue group". To put an issue into a "group", you can edit the issue and pick a relevant option for that custom field. Then, you can create a saved filter based on this custom field. The filter will find all issues in an "issue group" that the searched custom field option represents. Does this make sense? If issues need to belong to multiple groups, you can use a multi-select custom field, rather than a select list. Thanks, I don't really feel that using defined categories in a custom field is a good solution to this request. What I need is to create an ad hoc list of bugs that is limited in scope, either temporary or personal. Let me explain:
If I want to have a quick meeting to review the status of a few issues. I'd like to be able to send a URL to the meeting members to view the list of bugs. After that quick meeting, that particular list is no longer important. Using the custom field method would require editing those bugs. Since this list of bugs is ad hoc, limited in scope to only a handful of people in a short meeting, and no longer of interest after a few days, adding a custom field entry would clutter up the issues with garbage. The "custom field" method also requires permissions to edit the bug, which may not be available. Here's an example of how to do it in bugzilla: Using a custom field certainly has it's place, primarily when a set of bugs forms some coherent collection for a large set of users or for a long time, but it is not really what I am looking for. Thanks Yeah - that's the same functionality I'm after. e.g. for a project status meeting, a list of issues that is basically hand picked based on no filter of priority, etc.
Hi Zach,
Thank you for your feedback. May I ask if in bugzilla you have to specify the exact bugs you are looking for everytime you do this search? Thanks, Please see linked issues. While they were all created to address not being able to do the
type of search this issue reports, JRA-7772 reports same problem in the later comments. Just to let you guys know, I am implementing a Custom Field in which you can specify and list of Issue Keys in the Issue Navigator and have those issues returned, in the order you specified in the list.
Therefore you can search for "TEST-1, TEST-10, TEST-2" and only those 3 issues will be returned in that order. Once completed, I will include it in the JIRA Toolkit for people customer s to use and abuse. I am also looking at making it possible to re-order these items in the issue navigator, and add them to custom field through icons. The only thing it doesn't do is utilise the quick search. Let us know what you think. Cheers, Please (super pretty please) allow the keys to be cross-project (e.g. TST-10, JRA-42, RP-99)
Most of the filters created here are to track hot bugs across different projects so managers and Off topic: what is the deal with the view of this issue? In FF this thing is like landscape wide not portrait. I think Kevin and I are after the same thing and these are duplicate issues. I assume the functionality will not restrict based on being in the same project.
Kevin - the reason it's so wide is because JIRA doesn't wrap URL's, as in Zach Garner's comment on 26/Jul/05 09:26 AM. I guess you've never noticed that before 
Ahhh, yep never noticed that it didn't wrap the URL...I'm blind (and sometimes stupid).
It will be possible to have keys from any project.
WOOHOO!!! --> "It will be possible to have keys from any project."
I'm so glad this search capability is coming. If issue numbers are entered without the key, I hope that the field will assume the currently selected project. That's a very useful feature of Quick Search.
Yuck! ---> "If issue numbers are entered without the key, I hope that the field will assume the currently selected project."
I think this should depend on what you have selected in the project list of the search window. If you have the "All Projects" The cached project, etc. is problematic when doing a search. Many users here still fail to realize that when doing a search they Yes, that is better, Kevin. I had forgotten about the selected projects on the find page.
How is the Toolkit release for this functionality coming along?
That is not a bad idea at all! Though it hasn't made it into the first cut... maybe next release.
The toolkit is finished and is waiting on the 3.4 release Which once we sort one PITA websphere bug out will be released. Sorry about the delay. Cheers, Your previous comment suggesting using the currently selected project(s) if only a number was given.
Ahh ... gotcha. Well that is indeed good news that the toolkit will be ready for 3.4 ... thanks a million Nick, can't wait to test it out.
I may be a dunderhead, but I couldn't figure out how to use it. I installed 3.4 with the toolkit
and created a global custom field of type Multi Issue Key Searcher, but it doesn't show up in my search as a filter criterion with the other custom fields. When I did a mass edit, it didn't prompt me to edit existing issues... what is the way we are supposed to use this new feature? Hmmm ... just a guess (which you likely already did) but maybe you have to do a restart to load the new CF once you have it created.
I did a re-index, as suggested, and even a restart, as you suggested. I even added it to every screen.
Still, I only see it appear in the issue navigator as a selectable column. But I couldn't find any interface to set the values within it. Neal,
Can you please download and try the new version Sorry about the inconvienience. Cheers, Thanks Nick,
Got the new version loaded and tested and it works real good (with a couple of hitches): 1) key text is case sensitive, this could be a problem. 2) Doesn't discern between mixed separator values e.g., TST-1 AAA-1, BBB-1,CCC-1 (not a big deal though) 3) I don't think you had this slated for the first release but I'll mention it anyway ... it won't Primo addition though! Boss man should be tickled with this one. Thanks Kevin,
Yeah these should be no problem.
I think I would use the selected project(s) and return issues from those. Not sure when I will get a chance to revisit this field but I will get to it. Cheers, Just curious... on the documentation it says
"Once your results are displayed you can click on the column's header to get the sort options. You will be able to move individual issues up or down or remove them from the list altogether." but I couldn't get any arrows to display - just red X's - as in your screenshot. And yes - case insensitivity would be a nice improvement. I think I see the problem... the arrows only show up when the edit filter pane is showing. (View, not View and Hide).
Which makes sense since you're editing the filter. and then there's a further problem that clicking on the action makes the column disappear and so the action doesn't take effect. This was when I had an active saved filter with a column order that I was modifying and then chose to use my default column order rather than the filter's column order. After clicking on one of the actions, it reverts back to the saved filter's order. So, for the original request of being able to save a filter based on an issue list of keys, I think it is doing that. I don't get the order arrows at all ... ?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improvement
Open
Major
Allow for list of issues to be saved as a filter
I can't locate any other requests like this (though it does sound familiar).
What you can do is create a custom field (either multiselect or text) that can be used to store metadata.
You can then search on it and save it in a filter.
If you don't want the metadata to be displayed (only edited) you can create a new custome field type based on text or multiselct with out the the view templates. Quite easy to do.
Multiselect would allow you to select pre-defined metadata and text field will allow you insert any metadata (should be space seperated).
Would this suit your needs?
Cheers,
Nick