[#JRA-7771] Cannot specify "NOT NULL" in text searcher custom field

JIRA

Cannot specify "NOT NULL" in text searcher custom field

Created: 26/Aug/05 01:45 PM Updated: 11/Apr/08 03:53 PM

Component/s:

Custom Fields

Affects Version/s:

3.3

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

~~JRA-8200~~ Search/ filter for "not empty" (custom) fields

Participants:	Anton Mazkovoi [Atlassian], Kevin Wilson, Michael Hoefer, Michael Reker, Nick Menere [Atlassian], sameer danthurthy and Scott Farquhar [Atlassian]
Since last comment:	14 weeks, 1 day ago
Labels:

Description

« Hide

For custom text fields you may simply want to return any issue that has a non-empty value. We use a cf to cross-link technical support case id numbers with jira issues. Returning all the issues that are cross-linked is currently impossible ... managers hate that.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 29/Aug/05 02:46 AM

To do this currently you would need to create a new custom field searcher or create a new boolean hidden custom field that calculates its value from the you desired custom field. You can then show a checkbox in the Issue Navigator "Show all cross referenced issues".

[ Permlink | « Hide ]

Kevin Wilson - 29/Aug/05 11:21 AM

Huh?

Now wouldn't it just be simpler to allow a wildcard to be used in custom text fields?

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] - 29/Aug/05 06:57 PM

Kevin,

I'll leave this issue open as a request for enhancement. Nick's suggestions were a workaround if you wanted this feature today.

Cheers,
Scott

[ Permlink | « Hide ]

Michael Reker - 01/Aug/07 05:45 AM

@Nick,

Can you explain me how I can deploy your workaround?

Or is there possibly a better solution, although I guess this is still an open issue (after I found multiple issues concerning the same problem)

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 02/Aug/07 02:46 AM

Michael,

Nick is talking about writing a custom plugin that would have to be written in Java and deployed to JIRA. More information on JIRA plugins can be found here:
http://confluence.atlassian.com/display/JIRA/How+to+create+a+new+Custom+Field+Type

The other solution is to add the field to the issue navigator and then sort by the field. This will group all the issues that have this field empty and non-empty together. However, if there are a lot of issues in the results, then this could be a bit slow.

At the moment, these are the only work arounds I am aware of.

Cheers,
Anton

[ Permlink | « Hide ]

Michael Hoefer - 03/Nov/07 01:47 AM

Atlassian, I don't see how this can be a Minor issue, please. For all of its strengths, Jira's biggest weakness is querying. No equivalent of 'not null', no and/or control, no multiple users or groups allowed, and at least with our implementation with a few custom fields, a very long-scrolling filter pane.

So can you comment on overall enhancements you have in the works for Filters?

Thanks much

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 04/Nov/07 06:42 PM

Hi Michael,
I am assuming this work will be done in conjunction with JRA-1560 (which does have a priority of Major). We do believe this is a big hole in JIRA functionality but for JIRA 4.0 we are concentrating Sharable Dashboards (our most requested open feature).
Unfortunately we can not commit to a date for this feature at this time, though we do consider it to be one of the most important outstanding feature requests for JIRA.

Cheers,
Nick

[ Permlink | « Hide ]

sameer danthurthy - 11/Apr/08 03:53 PM

In fact, rather than just leaving it as null/not null, if it supported regex, it would be great. RegEx is supported in lucene and so why not here?