Jira uses a powerful logging module called log4j for runtime logging. For all of the following procedures, you must be logged in as a user with the Jira System Administrators global permission.
The logs are written to the log subdirectory of your Jira application home directory (or elsewhere if you have configured a different location). You can view the location of the atlassian-jira. Log in the ‘File Paths ‘ section of the system information page.
There are five logging levels available in log4j: ‘DEBUG’, ‘INFO’, ‘WARN’, ‘ERROR’ and ‘FATAL’. Each logging level provides more logging information that the level before it: ‘DEBUG’ provides the most verbose logging and ‘FATAL’ provides the least verbose logging.
What is Jira and how does it work?
When launched in 2002, Jira was purely issue tracking software, targeted at software developers. The app was later adopted by non-IT organizations as a project management tool.
How did Jira get its name?
As we developed our own bug tracker, and then it became an issue tracker, the name stuck, but the Go got dropped – hence JIRA! Further investigation into the name has revealed that Gorira is Japanese for “gorilla”, whilst Kujira is Japanese for “whale”. So Gojira is roughly translated to mean “gorilla the size of a whale”!
Another thing we wondered was; when did Jira become a project management tool?
The most usefull answer is; the app was later adopted by non-IT organizations as a project management tool. The process sped up after the launch of Atlassian Marketplace in 2012, which allowed third-party developers to offer project management plugins for Jira.
One article argued that built for new Jira users, this learning path of self-paced courses will help you get up and running in Jira in just 90 minutes. Start with key concepts like issues, projects, and boards, then discover how to navigate Jira and manage your work .
How do I enable profiling in Jira?
Permanently — profiling will remain enabled, even after you restart Jira. Select System support > Logging & Profiling to open the Logging page, which lists all defined log4j categories (as package names) and their current logging levels. Scroll to the ‘Profiling’ section at the end of the page.