Project

General

Profile

Actions

Feature #9790

closed

Allow filtering text custom fields on "is null" and "is not null"

Added by Pierre Pretorius about 13 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Category:
Custom fields
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

We have a custom field called "Test Case ID" that might be populated. We want to create a public custom query that shows all issues that have this field populated, in other words we want to query where Test Case ID is not null. If you set the filter to "is not" and leave the text box blank, it shows an error message that the text box must be entered. Please add "is not null" to the dropdown or allow the text box to be empty. This scenario is occurring more and more with a few different fields.

Thanks for the excelent work with Redmine!


Files

is_not_null.png (7.58 KB) is_not_null.png Pierre Pretorius, 2011-12-13 14:30

Related issues

Has duplicate Redmine - Feature #4815: More criteria for filtering ticketsClosed2010-02-11

Actions
Actions #1

Updated by Pierre Pretorius over 12 years ago

  • Assignee set to Jean-Philippe Lang

I'm really sorry for assigning this to you, can you please evaluate this request and put it in as a candidate or throw it in your dustbin/will not implement status? Thank you.

Actions #2

Updated by Jean-Philippe Lang over 12 years ago

  • Subject changed from Allow filtering fields on "is null" and "is not null" in issue queries to Allow filtering text custom fields on "is null" and "is not null"
  • Status changed from New to Resolved
  • Target version set to 1.4.2

Added in r9671.

Actions #3

Updated by Jean-Philippe Lang over 12 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Fixed

Merged.

Actions #4

Updated by Go MAEDA almost 6 years ago

  • Has duplicate Feature #4815: More criteria for filtering tickets added
Actions

Also available in: Atom PDF