| Key: |
JRA-9860
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Kerstin Klein
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
JIRA
Created: 09/Apr/06 11:24 AM
Updated: 18/Apr/06 03:22 AM
|
|
| Component/s: |
Administration
|
| Affects Version/s: |
3.3
|
| Fix Version/s: |
None
|
|
|
We 've built a custom field (multi select) "server type" containing 3 possible values. if we use a filter on this field we'll find all of type 1, type 2 or type 3. unfortunately it's not possible to find out only those ones which are assigned to "none".
|
|
Description
|
We 've built a custom field (multi select) "server type" containing 3 possible values. if we use a filter on this field we'll find all of type 1, type 2 or type 3. unfortunately it's not possible to find out only those ones which are assigned to "none". |
Show » |
|
mandatory flag on custom fields or possibility to search for empty values
It is possible to make fields required. For more information see:
http://www.atlassian.com/software/jira/docs/latest/issuefield_configuration.html#requirefield
The feature request for searching for issues with no custom field value is tracked by JRA-6180. Please vote for it.
At the moment the only way to get around the searching limitation is to find issues using another criteria, add the custom field to the list of displayed columns and then sort by the custom field value.
Thanks,
Anton