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

Deploying a servlet in JIRA


We all know how useful a servlet is! JIRA provides an easy way to deploy a JAVA servlet with the help of the Servlet plugin module. In this recipe, we will see how to write a simple servlet and access it in JIRA.

Getting ready

Create a skeleton plugin using the Atlassian Plugin SDK.

How to do it...

Following are the steps required to deploy a JAVA servlet in JIRA:

  1. Include the servlet plugin module in the atlassian-plugin.xml file. The Servlet plugin module allows the following set of attributes:

    a. class: This is the servlet Java class and it must be a subclass of javax.servlet.http.HttpServlet. This attribute is mandatory.

    b. disabled: This indicates whether the plugin module should be disabled or enabled by default. By default, the module is enabled.

    c. i18n-name-key: This is the localization key for the human-readable name of the plugin module.

    d. key: This represents the unique key for the plugin module. This attribute is mandatory.

    e. name: This is the human-readable...