[#JRA-4208] Able to define default sort order in different page

JIRA

Able to define default sort order in different page

Created: 12/Aug/04 03:07 AM Updated: 22/Aug/08 05:30 PM

Component/s:

Filtering & Indexing, Issue navigator

Affects Version/s:

2.6.1 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. Sort1.jpg
(125 kB)

2. Sort2.jpg
(118 kB)

3. Sort3.jpg
(196 kB)

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-14482~~ Allow users to set a default sort in their Issue Navigator config

~~JRA-9412~~ Allow default sort order in Issue Navigator

Reference

This issue relates to:

JRA-8852 Sort filter results by non-visible field

JRA-3219 Specify sorting on filters

JRA-11134 Allow setting of column order/sort with no issues in result set

Participants:	Anton Mazkovoi [Atlassian], Dampsoft, Edgar Li, Johnathan James, Mei Yan Chan [Atlassian], SIT Administrator and Torley Linden
Since last comment:	11 weeks, 4 days ago
Labels:

Description

« Hide

We are using version 2.6.1 enterprise. Would like to know how to define default sort order for issue navigator, or any other views?

Thanks,

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Mei Yan Chan [Atlassian] added a comment - 17/Jul/06 04:18 AM

The workaround to this problem would be to modify the com.atlassian.SearchRequest Java class at the getSearchSorts() method by substituting the second parameter of the searchSorts.add() method.

Please refer to the com.atlassian.IssueFieldConstants Java class for the required constant. It could be PRIORITY, STATUS etc. For instance,

searchSorts.add(new SearchSort(NavigableField.ORDER_DESCENDING, IssueFieldConstants.PRIORITY));

Regards,
Mei

[ Permlink | « Hide ]

Torley Linden added a comment - 22/Jun/07 01:42 PM

Jeremy of Atlassian pointed me here. I'd really like to have a diff. sort order for quick search – specifically by Updated, because I use it to hunt for fresh issues all the time and find myself repetitively sorting after-the-fact.

[ Permlink | « Hide ]

Johnathan James added a comment - 13/Jul/07 01:29 PM

At work, we are using Enterprise Edition, Version: 3.6.5-#161, and I still don't see an option for setting a default sort.

I just wanted to add my comment to say this would be a great option to have.

Thanks!

[ Permlink | « Hide ]

Dampsoft added a comment - 05/Feb/08 07:56 AM

Hi, we are using version 3.11, we like to set a default sort order which represents the order in which issues should be resolved.
Since the issue is still open I guess this feature is not jet implemented?
Or do we have to compile jira for these customisations?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 05/Feb/08 09:35 PM

Hi,

Since the issue is still open I guess this feature is not jet implemented?

Yes, unfortuantely, we were not able to get to this one as we have a lot of improvement and new feature requests. For more information on how these are scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Or do we have to compile jira for these customisations?

At the moment the only way is to change JIRA's source code and rebuild JIRA.

Cheers,
Anton

[ Permlink | « Hide ]

SIT Administrator added a comment - 22/Jul/08 02:28 AM - edited

Screenshot1 -> Sorting on Key (first sort order).

[ Permlink | « Hide ]

SIT Administrator added a comment - 22/Jul/08 02:30 AM - edited

Screenshot2 -> Sort on Fix Version/s (first sort is Fix version/s second sort is key)

[ Permlink | « Hide ]

SIT Administrator added a comment - 22/Jul/08 02:31 AM - edited

Primary and secondary sorting is wrong. SpcQualityExecution should be grouped together at the top. Then they should be sorted according Key. Now we have two rows at the top and then one row at the end.

This is also stated in the small text to the left: "Sorting on Fix Version/s THEN on key".

As you can see it groups projects together. So the real sorting is: "GROUPED on project, THEN sorted on Fix Version/s THEN sorted on key". Because of this grouping on project we always need to export to excel to do a real primary sort on Fix Version/s and secondary sort on Key.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 22/Jul/08 11:39 PM

Hi SIT Administrator,

I believe this issue is not about the same thing you are reporting.

Please note that when sorting on versions, the sort is done by project and then by version sequenc, not the version name. The order of versions can be defined in the Manager Versions secion under Project Admin.

One way to get an alphabetical sort on versions is to export the search results to Excel and then sort there.

Cheers,
Anton