|
[
Permalink
| « Hide
]
Jeff Turner [Atlassian] added a comment - 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 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 PLEASE resolve this issue!!
A text searcher that supports searching for "none"
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). This is necessary to build the plugin
This is the compiled jar file for the plugin.
I've made it easier for people to try this idea out. The latest attached file customfield-search-plugin-1.0.jar provides the new search type.
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 Hi Bettina,
Just out of interest, what was the failure with Jira 3.9.1? ~Matt 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. ***************************************************************************************************** Looks like the jar file was built with jdk1.6 instead of 1.5. I'll upload a
1.5 version as well ~Matt Go to Manage Attachments and use the jar file uploaded on 11/29 if you are using jdk1.5 for Jira
Hello Matt,
thank you for uploading the second .jar! Bettina Glad it worked for you. Now we just need some comment from Atlassian about the wisdom of this approach.
Jeff, Anton, or Ian: please would someone chime in here. ~Matt Hi Matt,
I had a brief look at the classes. I think the approach is good. Please note that the plugin will not work on JIRA 3.11 as Lucene has been upgraded to version 2.2, where Field.Text and Field.Keyword have been removed. It should be easy to get around this by using the constructors of the Field object, see the Lucene Javadoc As you have mentioned, using this plugin on a large set of issues could result in bad performance. As far as I can tell, another affect of this is searching for "customfield_xxxx", where xxxx is the id of the custom field, will return all issues with the custom field having some value. (I have not actually tested any of this). Cheers, The source for the plugin for Jira 3.11
The plugin jar file for Jira 3.11
Anton, thanks for the response. Does Atlassian have a different approach in mind for implementing this feature?
I nearly ended up writing a plugin to provide raw SQL read-only access to get this working. I've attached a zip file with the source and a version 1.0.1 jar file for the plugin that should work with Jira 3.11 in case other people want it. ~Matt Hi Matt,
At the moment I do not have a detailed technical spec for how we are planning to do it. My personal thinking is adding a flag to the Lucene document when the field is empty e.g. customfield_xxxx_empty: true. This will involve changing how the search sub-system works in JIRA, which will take some time. We will need to assess if this solution is viable when we schedule this feature. Cheers, Fair enough. BTW, the performance of the MatchAllDocs was better than I
expected. Selecting 2K from 18K issues took less than 2s for me. ~Matt On Dec 4, 2007 8:20 PM, Anton Mazkovoi [Atlassian] (JIRA) <
Thanks for the update. I expected it to be slower than this too. However, 2s is fairly taxing. Lots of JIRA users have a lot more than 18k issues. We also rely on searching being sub-second so that we can display search counts for saved filters on various pages. Yes, it's probably worth testing the different approaches to see where the
breakpoints are. ~Matt On Dec 6, 2007 3:45 PM, Anton Mazkovoi [Atlassian] (JIRA) < This is definitely one of the most important feature I am missing in JIRA.
We need the ability to search for text values that are not empty. We have this feature in bugzilla and the lack of it in Jira may prevent us from switching products.
I also want to be able to search for issues where a certain field is set to any value (i.e. !=null)
BTW just noticed... this feature request is nearly 3 years old!!! This one is also a problem for me. I have to create a dummy value for certain fields, make it the default, and then make the field be required. This seems to work, but then I have an issue dealing with the older tickets that existed prior to the workaround. I have to search for those using the filter-and-sort trick, then update those issues to use the dummy value for the field. It ends up being a whole lot of extra work.
I would like to be able to search for "null" and also search for "not null" on custom fields.
We also need the possibility to search for empty or not empty fields.
Is there any time line decided on this issue??
Any update will be good for us. Relating this to JRA-1560 as we are going to allow isempty/isnull JQL queries to execute.
I will be out of the office on a business trip. I will be back in the office on January 19th.
– En este momento estoy fuera de la oficina. Estaré de vuelta el 19 de Enero. Med venlig hilsen / With best regards / Saludos I will be out of the office on a business trip. I will be back in the office on January 19th.
– En este momento estoy fuera de la oficina. Estaré de vuelta el 19 de Enero. Med venlig hilsen / With best regards / Saludos Adding another vote for this. Not being able to search for an empty Version number using the version searcher really sucks. The workaround (searching for all, then sorting by the version field, then manually selecting all of the empty ones) REALLY sucks. Please fix!!!
P.S. This is the first time I've come to this site looking for a feature and didn't find what I was looking for! I will be out of the office until March 3rd. Please contact Bhagat Nainani for any urgent issue.
– En este momento estoy fuera de la oficina hasta el 3 de Marzo. Por favor contactar a Eduardo Rubio por asuntos urgentes. Med venlig hilsen / With best regards / Saludos I would also like the ability to search for a blank text field, e.g. "Original Estimate" I want to know if all the issues have an estimate entered.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Blocker
Search/ filter for "empty" fields
.