When ordering by custom field, software projects are grouped together followed by JSM

[JT Wieme]

I'm using a filter to show all issues assigned to a certain user that have a particular custom field filled in. I also want to sort by that custom field. I am able to get results across all projects (software and JSM) however, the software projects are listed first and sorted by the custom field then the JSM projects are listed and sorted by the custom field. I do not get a full list of issues with the desired sort order. 

Interestingly, it appears that this delineation between software and JSM does not happen when ordering by default fields (e.g. reporter).

Is there a way around this?

Screenshot showing this, the email icon are issues in JSM projects --

[John Funk]

Hi JT - Welcome to the Atlassian Community!

Can you share the actual JQL query? 

[JT Wieme]

Hi thanks! 

Yes it's this:

assignee = 5e4efc582110470c8da224c4 and statusCategory!= done and "Personal Priority[Dropdown]" is not EMPTY ORDER BY cf[10185] ASC

cf[10185] is the "Personal Priority" field I'm attempting to sort by.

[John Funk]

Well, that is indeed weird. Just for fun, what happens when you change it to DESC instead of ASC?

[Trudy Claspill]

Hello @JT Wieme 

Welcome to the Atlassian community.

Are the projects Company Managed or Team Managed or some of both?

What is the field type of the custom field?

Is it the same custom field with a global context being used in all projects?

[JT Wieme]

Thank you!

The JSM projects are team managed and the Software projects are company managed.

The field type is Select List (single choice).

And yes, that custom field has a global context being used in all projects.

[Trudy Claspill]

Can you use the option described on the following page to retrieve all data for one of the Service Management project issues, and for one of the Software project issues where the same value is being used in the custom field?

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

The output should include both the human readable value (i.e. "2") and the option id, which will be a multi-digit numeric value. 

Try this to confirm that the selected option shows the same multi-digit numeric ID in both issues.