Summary

When sorting issues by a numeric field that has null values JIRA behaves differently when comparing Jira Issue Search and Advanced Roadmaps.

Steps to Reproduce

1. Having 3 issues with value for a custom field as 10, 20, and null
2. Run JQL query: ORDER BY <custom_field> ASC

Expected Result

JIRA should order the issues the same way in both places

Actual Result

Jira Issue Search places the null value at the lowest rank
10
20
null

However, in Advanced Roadmaps using the same filter, it places the null value at the highest rank
null
10
20

Workaround

Currently, the only workaround is to set a value to the field in all issues returned by this filter where the field is empty.