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

Re-ordering fields in the View Issue page


JIRA has highly configurable screen schemes and field configuration schemes. These schemes let us use different screens for different operations and allow us to configure the screens to show/hide fields, make fields mandatory, change the order of fields, etc.

While this works on most screens, JIRA's View Issue page is an exception. We can hide/show fields from this screen but there is no easy way to reorder the fields on this screen using configuration options.

For example, in the view issue page, the summary of the issue is followed by standard issue fields like status, priority, versions, components, and so on. It is then followed by custom fields, and then comes the description of the issue. This can sometimes be a pain, for example in cases where description is the most important field.

Following is how the view issue page looks when you have a large custom field:

As you can see, the Not so important field is an unlimited text field, which has a...