With respect to the following feature:
http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options#ConfiguringJIRAOptions-advanced

A customer added a comment to the following page, indicating that the jira.issue.actions.order property (now stored in the DB) has no effect at all.
http://confluence.atlassian.com/display/JIRA/Changing+the+Default+Order+for+Comments+from+Ascending+to+Descending?focusedCommentId=254312459#comment-254312459

I've tried modifying this value through the Advanced Settings page too to find doing so has no effect either. However, I haven't yet tested modifying this in the jira-config.properties file, although the customer verified that this worked.

Could you please investigate this issue further? From what I can see, there are two solutions here:

• Fix the DB-stored property behaviour so that it works.
  • From a customer's + tech writer perspective, this is the preferable option.
• Remove this option from the UI.
  • I suspect this is the easier dev option, but doc rework is required.

Nevertheless, please advise on the solution you choose as it will affect the documentation.