Oldest comment first by default in Jira 9.0.x

[Matt Nolley]

The latest Jira Server versions grant users the ability to order comments and other activity entries in either oldest-first or newest-first order.  That's a welcome feature, but it defaults to newest-first.  We've had comments configured to display as oldest-first for years now, a setting our users almost universally prefer, but comments now default to newest-first.  Users can click the sort-order control to change that, but it's deeply annoying to have to do that every time you view an issue.  Has anyone come across a way to change this behavior?  The jira.issue.actions.order property no longer appears to have any effect.

[Sreenivasaraju P · Accepted solution]

Hi @Matt Nolley ,

I am correcting my response. 

I have changed jira.issue.actions.order to asc in Advanced Settings and logged in again. It is working fine, showing oldest comments first. But after any ticket and added new comments, automatically it is changing to newest first. For the tickets it is showing comments in the newest first order. If I log out and login again, it is showing oldest first.

Looks like , it is a bug, we need to report to atlassian.

[Matt Nolley]

What's bizarre is that now, after I flip-flopped jira.issue.actions.order back and forth between desc and asc several times in testing, it's now working correctly consistently.  I'm not seeing the same behavior you report.

[Andrey Tetyuev]

The JIRA administrator can configure the default comments sorting-order for all users at once in the configuration of JIRA-instance.

Starting from versions v9.13.0 , v9.12.6 and v9.4.19 the related user-own settings will be stored persistently (i.e. user will be able to change the order). Please see the Issue https://jira.atlassian.com/browse/JRASERVER-5443 for details.

[Florian Bonniec]

Hi @Matt Nolley 

You may have to raise a support ticket to Atlassian.

I think the  jira.issue.actions.order is the right parameter to change, so if it do not works, it's may be a bug introduced in JIRA 9.X.

Just to let you know that this parameter is working as expected on JIRA  v8.22.3

Also have you check if it' s not a cache issue ?

Regards

[Neal Culiner]

Still not working right for me 9.latest. I've tried changing to asc and removing it, it will not persist or work reliably. Hopefully someone reported it to Atlassian to be fixed. We hate newest first.