|
In several JIRA installations I've used at several companies (not strictly for software development, but for issue management of various production processses), people use custom fields for specific IDs relating to issues (e.g. item numbers, page numbers, etc). We put them in custom fields in order to give the reporters (usually end-users) some structure and to make sure we get all the info we need. On the technician/developer/etc side, though, one of the most frequent operations is to search for an issue by that structured identifier, which cannot be easily done. This improvement would siginificantly increase the productivity of our technicians.
We've migrated from Bugzilla and still have a lot of our notes and other internal references use the Bugzilla ID. We constantly are finding ourselves wanting to use the quick search field to look things up by Bugzilla ID, which is implemented as a custom field. I realize that there is a Bugzilla ID search portlet, but it's annoying to have to go to the dashboard and use a different search field. It would be extremely handy to have quick search handle everything.
We use JIRA to manage issues relating to our course bookings system, and often have to report these issues to the software developer. They, of course, use their own issue reference system, so we have a custom field which we use to record their reference against our issues. They are not very good at quoting our JIRA reference in their communications, so we always have to go into the 'Find Issues' function and do a long-winded search on the custom field there.
If we could choose which custom fields we wanted to be searchable by the Quick Search box, we could find and update issues more easily. We use a custom field for error stack information, and I've really missed the option to include this field in the Quick Search. At the moment, it is quite cumbersome to search for other issues with matching error stack information.
I'd like to see this get implemented. While its true that you can search on custom fields using the issue navigator "Find Issue". It is more convenient to use the "Quick Search" for text custom fields without having to click and scroll through the projects -> issue type -> custom fields and then enter in your query.
We have a large number of custom fields to do things like store hostname information for a problem report. It would be nice to have this lumped into the normal quick search. It would also be nice if custom fields could plug in to quick search (for example a custom field searcher that supports lookups on hostname or ip should be able to plug in to the quick search).
Being able to do such a search would eliminate the need for hacks like the comment in https://jira.ts.wikimedia.org/browse/WIKISENSE-9
 . Implementation could be as one checkbox for "All Custom Fields" that have text equivalents, or as checkboxes for each of the (currently 2 at Wikimedia) "Custom Fields" that have text equivalents (the former scales better but the latter allows more granularity). See also my similar report at https://jira.ts.wikimedia.org/browse/TS-74 . I have a ton of bugs from an old system and I want to search the old ticket numbers, but Smart Query thinks they are JIRA numbers and I get the "Issue Does Not Exist" error. I know I can use quotes, so that's a good workaround, but I would like Smart Query to be beefed up as above.
Maybe if you type a numeric search and it can't find a JIRA issue, it defaults to a proper field search? We are using the API with Flex/Coldfusion to allow users to submit tickets - we collect their login name as a custom value, and it would be great if we could key off that field when retrieving tickets to allow users to view a history and see their status (Jira is used a piece of a larger support dashboard)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Allow text custom fields to be searched from quick search / text search.
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=9770