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

Reports in Excel format


In the previous recipe, we saw how to write a simple report. We will now see how to modify the report plugin to include Excel reports.

Getting ready

Create the report plugin, as mentioned in the previous recipe.

How to do it...

The following are the steps to include the provision of exporting the report to Excel:

  1. Add the velocity resource type for the Excel view in the plugin descriptor if not added already:

            <resource type="velocity" name="excel" 
              location="templates/allissues/allissues-report-excel.vm" />
  2. Override the isExcelViewSupported method in the report class to return true. In our case, we add this in the AllIssuesReport.java:

            @Override
            public boolean isExcelViewSupported() {
              return true;
            }

    This method returns false by default, as it is implemented that way in the AbstractReport class.

  3. Override the generateReportExcel method returning the Excel view. This is very similar to the generateReportHtml we implemented...