|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Jeff Turner [Atlassian] - 09/Sep/05 06:25 AM
Yes, it's an unfortunate limitation in the search system. For now, a workaround is to sort by the relevant field. The first issues in the search will then be those with empty field values.
We already apply this workaround, but would need to have the search system enhanced.
Is there a feature request on your roadmap that I can vote for? I imagine that we are not the only JIRA users/ customers requesting this type of search. I couldn't find an existing issue. I've changed the type of this issue to record it.
I second the motion for allowing one to filter for a NULL Date Due value. I have several shared due date filters set up so staff can see what past due, due this week and due beyond next week. It would be great to be able to have a saved filter to also see what items do not have a due date.
I would also like the ability to search for a blank text field, e.g. Bugnote Description.
Hello!
I'm also missing the possibility to search for empty fields. If I search for a jira system field of type user, for example "assignee", I can search for an empty value by selecting "unassigned". By the way it is not nice in Jira that the custom field searchers are so often different from the system field searchers. Cheers Also required is to be able to filter on the system value "none" for select lists
We have added a couple of custom fields for release handling. The information in these fields is of interest for certain parties, but only if they are filled in.
We would then want the ability to find all issues where these fields are "not null". We also need the ability to filter for empty fields.
Irene We also need to be able to filter on empty fields. Maybe you could add a checkbox beside every field called <Select if NOT NULL> ?
Yep. Searching on fields, including custom, which are NULL of NONE would be a big improvement
This functionality is very important to quality assurance proccess. In order to ensure that some special information is supplied correctly there must be some controls. There must be an oportunity of finding issues in which required informations have not been filled. So it will be possible to find people who doesn't conform to standarts. That's why I want to be able to know in which issues the particular fields are empty or null.
I know there is a workaround solution but as you know it is not effective, it is very cumbersome. For example currently, when I want to obtain a list of related issues I reach the results in 2-3 minutes in the event that I am lucky. But if there was such a utility with which I can filter issues according to their EMPTY-NULL fields it would take just a few seconds. Sometimes I have to consider two or three parameters at the sametime, so it takes even much time. Morover an extra bandwith is needed to download the unnecessary issues and there is an extra workload on the server. As a consequence solution of this problem will bring us a great convenience. Agreeing with most people here. This is sorely needed. In my case, I more specifically need to be able to search for dates which are either null or in a given range.
Agree that being able to filter on "blank" (or NULL or "" or whatever the syntax would be) is crucial – we'd like to create filters with this for various fields (e.g. "needs estimate", "needs priority", "unassigned" etc).
I second ( actually 15th
 ) this request, I've been asked numerous times for this and could not provide a proper solution Voting for it as well.. I am adding an enthusiastic and hopeful (???) vote #90 to this feature. We are sorely missing the ability to search for empty fields and especially 'unassigned' option for custom fields of type user picker or multi user picker. For example, we have a "QA Lead" field of type user picker and need to find all issues which are not yet assigned to a QA Lead. It's impossible right now, aside from the above cumbersome "Find All Issues and Sort by that Column" workaround. Please work on this.
I'm shocked to learn that this functionality is not included in Jira. This is a serious oversight in my view.
We are waiting for this feature as well. And btw, that workaround is poor...
For example, we have a policy that developers have to "analyze" all received bug reports by giving working estimates for them. Since you cannot create a filter where you list all issues that are UNRESOLVED and not estimated, this cannot be controlled in a simple way. This would be a very simple query to do in SQL, I just tried it. So could you please add this feature also to the JIRA client? We are currently using Jira Enterprise Edition, Version: 3.9.1. Hopefully additional comments and voting will help this issue be resolved soon! It is an important reporting capability to be able to create views where information has not been populated in custom fields.
For those looking for a different type of work around: 1. Make it a mandatory field up front I've just attached 5 files that provide a new searcher type for text fields. If you choose the new Enhanced Free Text Searcher type for a custom text field, and then reindex, you can use the search term "none" as part of your query and only issues with no content in the field will be returned.
Atlassian developers: this searcher adds an artificial value to every document with an indexable value. The query is a boolean of the Lucene MatchAllDocsQuery AND NOT artificial_value as suggested in the Lucene FAQ Apart from the potential performance issues with large numbers of issues, does this approach have other drawbacks that I am missing? Usage To use the files, first read up about creating your own plugins, then create a directory structure like: project.xml Compile with maven 1.x as usual, and deploy the resulting jar file. This has been tested with Jira 3.10 but probably works with earlier versions (Lucene 1.9+ is needed I think). I just tried out the .jar with jira 3.9.1, it does not work with that version.
I'll check it again when doing the next jira upgrade. Bye Bettina Zucker Hello Matt,
here is the error log of my test yesterday: 2007-11-28 14:32:39,547 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were problems loading the module 'customfield-searcher'. The module and its plugin have been disabled. ***************************************************************************************************** | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improvement
Open
Blocker
Search/ filter for "empty" fields
.