The Issue Navigator displays results grouped by Project regardless of what column the filter results are ordered by.

When the results of a filter are set to be ordered by fixVersions they are but only on a group by group basis. The groups being each individual Project.

To make the problem even more interesting is the fact that this grouping only applies to issues that actually have a fixVersion set. Issues that do not have a fixVersion set are then listed in what appears to be no apparent order.

This is the case in both v3.13.5 and v4.0.2.

We are trying to create a filter that selects issues across all JIRA Projects that have a custom field set to a specific value and then order them by fixVersion.

The JQL for this filter is:
"Business Initiative" = "Production Committee" ORDER BY fixVersion ASC

You will see the first two pages of the results in the two attached screen shots.

Screen shot #1 shows issues that have a fixVersion value set. They are obviously not sorted strictly by the fixVersion field. In actuality they are sorted first by Project Key prefix and then by fixVersions.

Screen shot #2 shows issues that do not have a fixVersion value set. These are obviously NOT being sorted first by the Project Key prefix.

This bug in effect means that sorting by any field other than Key cannot be achieved!