Issue Details (XML | Word | Printable)

Key: JRA-4978
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Mike Aizatsky
Votes: 4
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Add range search ability to Number field type

Created: 19/Oct/04 06:54 AM   Updated: 02/Sep/05 04:04 PM
Component/s: Custom Fields
Affects Version/s: 3.0
Fix Version/s: 3.3 Beta1

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. screenshot-1.jpg
(105 kB)
Issue Links:
Duplicate
 

Participants: Jeff Turner [Atlassian], Kevin Wilson, Mark Chaimungkalanont [Atlassian], Mike Aizatsky and Scott Farquhar [Atlassian]
Since last comment: 3 years, 13 weeks, 2 days ago
Resolution Date: 25/Jul/05 04:43 AM
Labels:


 Description  « Hide
Should support searching for range: 220 <= x <= 240

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Kevin Wilson added a comment - 26/Aug/05 01:35 PM
this does not work in 3.3 Pro

search on number field that has integer values using:

0 <= x <= 999999

and no results were returned. the custom field has tons of values in it.


Mark Chaimungkalanont [Atlassian] added a comment - 28/Aug/05 08:43 PM
Kevin,

Have you reindexed JIRA after changing the searcher type? You will have to do this manually when you change the searcher for a field (see JRA-4641 ).

Let us know if this still doesn't work.

Cheers

Mark C


Kevin Wilson added a comment - 29/Aug/05 10:54 AM
I never changed the searcher type but that aside, I did reindex and it still doesn't work.

Scott Farquhar [Atlassian] added a comment - 29/Aug/05 06:59 PM
Kevin,

Can you perhaps attach screenshots showing what you are doing, and what you are trying to achieve? I think that would be the easiest way to show us what is happening.

Cheers,
Scott


Kevin Wilson added a comment - 30/Aug/05 09:19 AM
I enter the string just as the reported issue states to return all issues that contain a VIID number.

Jeff Turner [Atlassian] added a comment - 02/Sep/05 05:44 AM
Kevin,

You are still using the 'Number Searcher' on your custom field. You need the 'Number Range Searcher', which provides two fields, min and max.


Kevin Wilson added a comment - 02/Sep/05 04:04 PM
Ahhh! ... sometimes my idiocy amazes even me.

Thx for the info.