We have Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc) How can we disclose stack traces in some errors. I have seen this solution https://confluence.atlassian.com/pages/viewpage.action?pageId=282174657but it does not work for us because there is no 500page.jsp file. How can we manage what is seen in stack traces?
We have also tried to change error500.soy, but than we get the standard tomcat 500 error.
How to solve this issue?
Same problem here. Sometimes I see that ajax requests fail with a 500 status, but JIRA doesn't log the stacktrace in the log file, so it's impossible to find out what exactly failed and why.
I can't believe that actively NOT showing stacktraces is some kind of feature? Logging any exceptions after a 500 should be the default.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs