Changing actions order is causing inconsistency results on issue tabs

Changing the actions order in Advance Settings (jira.issue.actions.order) to ASC makes History, Worklog and All tab behave weirdly.

Behavior of "Oldest fist" order

Comment: Loaded 10 latest comments in ascending order and "Load 10 older comments" button available at top to load more older comments.

All: Loaded 10 oldest events in ascending order and "Load 10 newer events" button available at bottom to load more newwer events. However we also see another button "Load 10 older events" available at top. When we click the button at top, we see duplicate event of "created issue".

Work Log: Loaded 10 oldest work logs in ascending order and "Load 10 newer work log" button available at bottom to load more newer work log.

History: Loaded 10 oldest history in ascending order and "Load 10 older history items" button available at bottom to load more newer history items.

Steps to reproduce

• Navigate to Administration → System → General Configuration → Advanced Settings.
• Modify the property jira.issue.actions.order to ASC.
• Observe this in an issue that has enough actions to cause them to be collapsed after a certain number.

Expected Results

Jira will follow consistently the setting. Not change from tab to tab. The behavior of all the tabs under "Activity" section to be consistent.

Actual result

Jira is not giving consistent results are described above.

Workarounds

For consistency, you would have to revert back to Newest First as it's working as intended.