Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Range filters on scripted fields don't work when bounds aren't explicit #4950

Closed
epixa opened this issue Sep 15, 2015 · 0 comments
Closed

Range filters on scripted fields don't work when bounds aren't explicit #4950

epixa opened this issue Sep 15, 2015 · 0 comments
Labels
bug Fixes for quality problems that affect the customer experience PR sent v4.1.3

Comments

@epixa
Copy link
Contributor

epixa commented Sep 15, 2015

If either operand of a range filter is infinite (ie. the user does not specify an upper or lower bound), then a fatal error occurs. This bug already submitted and a fix is under review for 4.2, but that fix will need to be backported for 4.1.3.

Original issue: #4862
4.2.0 PR: #4948
@epixa epixa added bug Fixes for quality problems that affect the customer experience v4.1.3 labels Sep 15, 2015
@epixa epixa mentioned this issue Sep 16, 2015
Merged
@epixa epixa added the PR sent label Sep 16, 2015
@Bargs Bargs closed this as completed Sep 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience PR sent v4.1.3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@epixa @Bargs