Problem Definition

Some actions in Jira are run in long transactions - e.g. issue create or issue status transition.

When some code requests a rollback, the whole action is reverted. If that code doesn't provide any logging, it's impossible to check what code and why requested the rollback.

Suggested Solution

Jira should provide an optional, low-level log that would generate a stacktrace, allowing Jira admins and Atlassian Support Engineers to troubleshoot such issues.