Number sorting not working in Advanced Search

[Andy Lutz]

In my JPD projects, I have a number field called "Release Priority", which teams can use to to assign a priority to their ideas and use it to sort by priority. Within a given project, sorting by this field (ascending and descending) works as expected:

However, when I look at the same issues in Advanced issue search and try to sort using this field, the ideas are not sorted as I would expect (i.e. no sorting occurs):

Note how when I change the sort order, the ordering of the numbers does not change.

I was wondering if anyone else had experienced this issue, or if it's expected?

Thanks!

[Simone Longoni]

Ciao @Andy Lutz !

It looks like that the field you defined (Release Priority) is a combo/select field type (the user selects between a possible list of values): in such cases, I think you need to add Weight for each of those field values, so that filtering knows what to sort against.

Otherwise they are just labels and the maximum you could expect is to have an alphabetical sorting (that would work from 1 to 9...).

Anyway, please give it a try to adding weight to each of those... and let's our fingers crossed! :-)

[Andy Lutz]

Hi @Simone Longoni !

The field is actually a "Number field" (in the first screenshot that's indicated by the "123" label next to it). As a result, I can only input numbers and not add weights.

Thanks for the suggestion though!

[Deleted user]

I have something similar when I try to add sum to grouped items. It simply doesn't respond. 

[Andy Lutz]

@[deleted] there seems to be something buggy with Number Fields in particular. I've recreated the field with a new name, and that one is sorting properly. I'll summarize what I've found in the main thread.

[Andy Lutz]

As an update, I created a new "Number Field" called "*Release Priority", the only difference being the name of the field ("*Release Priority" vs. "Release Priority"). And in this case, the field sorts properly both within a Project, as well as in Advanced Issue Search.

Project Sorting:

Advanced Issue Search Sorting:

There isn't any difference in the field definition/how the field was created, here's the settings for each field:

I'm not sure why "Release Priority" will NOT sort in Advanced issue search, while "*Release Priority" will, given that their settings are exactly the same.

I appreciate any help!

[Hermance NDounga]

Hello Andy, 

Thanks for raising this bug. Unfortunately we are aware of some faulty behaviours on the advanced issue search, and we've been raising them to the team in charge of this part of Jira, and they are actually currently working on a new experience for it. 

On my side, I'd be interested to understand what is your use case for the advanced search - or why do you need to perform this action there and not in Jira Product Discovery? 

(Please feel free to share only what you want to share, but it would be interesting to understand if we could improve something in Jira Product Discovery :) ) 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

[Andy Lutz]

Thank you @Hermance NDounga for the update!

My use case for using Advanced Issue search is to combine ideas from separate JPD projects into one single view.

Specifically, we have a large number of Product teams, that I need to separate in to multiple JPD projects due to access policies. In this case, having one JPD project with all Products teams in there (which would give a "combined" view) doesn't work, because I can only control access at the project level. As a result, I'm creating separate projects for each Product team, to ensure that we can grant access to the roadmaps on a product by product basis.

However, I still need to have a "combined" view across products of the roadmap for leadership. So my workaround for now is to pull in multiple JPD projects/ideas into Advanced Issue Search, which allows me to aggregate product teams and their ideas/features together in one place.

A "multi-project view/project" that could aggregate multiple projects together (while still allowing for us to control permissions) would be the ideal solution.

Hopefully that makes sense, happy to provide any additional context!

Andy

[Hermance NDounga]

Hi Andy, 

Thanks a lot for your answer. I understand your struggle, so I can just provide you with some update: at the moment we are exploring all topics related to global entities, so global fields, templates, global views etc... at the moment, we are prioritizing global field as we think it's the basic/core element for aggregation of any sort :) 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

[Andy Lutz]

Thank you Hermance! Assuming "global fields" means creating fields for JPD that then can be share across projects, I agree that that should be prioritized over a multi-view.

I appreciate the insight!

Best,

Andy