Disable Stack/trace methods

[Prabhu]

How to configure Jira handle all errors and must not display any debug information or verbose messages thus revealing sensitive parameters?

[Nic Brough -Adaptavist-]

You don't.  It's designed, like all good systems, to tell you what is going wrong.

[Nic Brough -Adaptavist-]

No.  That's a vast oversimplification, and not helpful at all.

You absolutely should upgrade if you want to reduce the problem.  In Atlassian applications (like most others) stack traces only go to users when the application is not coded to catch them properly and present something nicer.  Upgrading will reduce the frequency of that, as more areas catch and handle them.

Also, stack traces that users see don't contain debug information that reveals sensitive information.

[Steve Bachinsky]

Proper evaluation of what data constitutes "sensitive information" is complex, and likely to become more so in the future.  Having the stack trace is helpful in a development and testing environment, but not in a production environment where the primary users will only be scared or disappointed.

There are environments where it is necessary to manage all data that is disclosed by an application, and the ability to minimize diagnostic logging data helps with that process.  Please consider adding a configuration knob to disable the logging of stack trace and other data that is not useful in a production environment.