Book Image

JIRA Development Cookbook - Third Edition

By : Jobin Kuruvilla
Book Image

JIRA Development Cookbook - Third Edition

By: Jobin Kuruvilla

Overview of this book

JIRA provides issue and project tracking for software development teams to improve code quality and the speed of development. With the new version of JIRA, you can create your own JIRA plugins and customize the look and feel of your JIRA UI easier than ever. JIRA Development Cookbook , Third Edition, is a one-stop resource to master extensions and customizations in JIRA. This book starts with recipes about simplifying the plugin development process followed by recipes dedicated to the plugin framework. Then, you will move on to writing custom field plugins to create new field types or custom searchers. You will also learn how to program and customize workflows to transform JIRA into a user-friendly system. With so much data spanning different projects, issues, and so on, we will cover how to work on reports and gadgets to get customized data according to our needs. At the end of the book, you will learn how to customize JIRA by adding new tabs, menus, and web items; communicate with JIRA via the REST APIs; and work with the JIRA database.
Table of Contents (18 chapters)
JIRA Development Cookbook Third Edition
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface

Enabling SQL logging in JIRA


Similar to access logs, another useful type of logging, especially when debugging an issue, is SQL logging. In this recipe, we will see how to turn on SQL logging.

How to do it...

Similar to access logs, SQL logging is also turned ON from the user interface at Administration | System | Troubleshooting and Support | Logging & Profiling.

Just as with access logs, the changes are temporary and will revert back in the next restart. Permanent changes can be made in the WEB-INF/classes/log4j.properties file, although this is not recommended because SQL access logs can take up a large amount of space and may adversely affect performance.

In such an event, the logging entry to be modified is as follows:

##################################################### # SQL logs ##################################################### # # Beware of turning this log level on. At INFO level it will log every SQL statement # and at DEBUG level it will also log the calling stack trace....