JIRA Development Cookbook

By Jobin Kuruvilla , Jobin Kuruvilla
    What do you get with a Packt Subscription?

  • Instant access to this title and 7,500+ eBooks & Videos
  • Constantly updated with 100+ new titles each month
  • Breadth and depth in over 1,000+ technologies
  1. Free Chapter
    Plugin Development Process
About this book
JIRA provides issue tracking and project tracking for software development teams to improve code quality and the speed of development.This book is your one-stop resource to master JIRA extension and customization. You will learn how to create your own JIRA plugins, customize the look and feel of your JIRA UI, work with Workflows, Issues, Custom Fields, and much more.The book starts with recipes on simplifying the Plugin development process followed by a complete chapter dedicated to the Plugin Framework to master Plugins in JIRA.Then we will move on to writing custom field plugins to create new field types or custom searchers. We then learn how to program and customize Workflows to transform JIRA into a user-friendly system. Reporting support in an application like JIRA is inevitable! With so much data spanning across different projects, issues, etc and a lot of project planning done on it, we will cover how to work on reports and gadgets to get customized data according to our needs. We will then look at customizing the various searching aspects of JIRA such as JQL, searching in plugins, managing filters, and so on. Then the book steers towards programming Issues, i.e. creating/editing/deleting issues, creating new issue operations, managing the various other operations available on issues via the JIRA APIs etc. In the latter half of the book, you will learn how to customize JIRA by adding new tabs, menus, and web items, communicate with JIRA via the REST, SOAP or XML/RPC interfaces, and work with the JIRA database.The book ends with a chapter on useful and general JIRA recipes.
Publication date:
November 2011


Chapter 1. Plugin Development Process

In this chapter, we will cover:

  • Setting up the development environment

  • Creating a Skeleton plugin

  • Deploying a JIRA plugin

  • Testing and debugging



Atlassian JIRA, as we all know, is primarily an Issue Tracking and Project Tracking System. What many people do not know, though, is the power of its numerous customization capabilities, using which we can turn it into a different system altogether! Maybe a helpdesk system, a user story management system, an online approval process, and a lot more. This is in addition to the issue tracking and project tracking capabilities for which JIRA, arguably, is the best player in the market.

So what are these customizations? How can we convert the JIRA we know into a product we want? Or maybe just add extra functionalities that are specific to our organization?

The answer to these questions probably can be summarized in a single word—plugins. JIRA has given the power to its users to write plugins and customize the functionality in a way they find suitable.

But is that the only way? Definitely not! JIRA itself provides a lot of customization options through its user interface, and in more demanding cases, using property files like jira-application.properties. In some cases, you will also find yourself modifying some of the JIRA core files to tweak functionality or to work around a problem. We will see more of that in the chapters to come but the best entry point to JIRA customizations are plugins. And that is where we start our cookbook, before we move on to the in-depth details.

What is a JIRA plugin?

So, what is a JIRA plugin? JIRA itself is a web application written in Java. But that doesn't mean you need to know JAVA to write a plugin, though in most cases you will need to. You might end up writing a simple descriptor file to add few links here and there. If that makes the non-Java developer in you happy, watch out for the different plugin modules JIRA supports.

A JIRA plugin is a JAR file that has a mandatory plugin descriptor and some optional Java classes and velocity templates. The velocity templates are used to render the HTML pages associated with your plugin, but in some cases, you might also want to introduce JSPs to make use of some pre-existing templates in JIRA. JSPs, as opposed to velocity templates, cannot be embedded in the plugin, but instead they should be dropped into the appropriate folders in the JIRA web application.

The plugin descriptor, the only mandatory part of a plugin, is an XML file which must be named atlassian-plugin.xml. This file is located at the root of the plugin. The atlassian-plugin.xml file defines the various modules in a plugin. The different types of available plugin modules include reports, custom field types, and so on, and these are discussed in detail in the next chapter.

The plugin development process

The process of developing a JIRA plugin can be of varying complexity depending on the functionality we are trying to achieve. The plugin development process essentially is a four step process:

  1. Develop the plugin.

  2. Deploy it into our local JIRA.

  3. Test the plugin functionality.

  4. Make changes and re-deploy the plugin, if required.

Each of these is explained in detail through the various recipes in this book!

JIRA, on start-up, identifies all the plugins that are deployed in the current installation. You can deploy multiple plugins, but there are some things you need to keep an eye on!

The atlassian-plugin.xml file has a plugin key which should be unique across all the plugins. It is much similar to a Java package. Each module in the plugin also has a key that is unique within the plugin. The plugin key combined with the module key, separated by a colon, forms the complete key of a plugin module.

Following is a sample atlassian-plugin.xml file without any plugin modules in it:

<!-- the unique plugin key -->
<atlassian-plugin key="com.jtricks.demo" name="Demo Plugin" plugins-version="2">
    <!-- Plugin Info -->
        <description>This is a Demo Description</description>
        <!-- optional  vendor details -->
        <vendor name="J-Tricks" url="http://www.j-tricks.com"/>
    . . . 1 or more plugin modules . . .

The plugin, as you can see, has details such as description, version, vendor-details, and so on.

When a plugin is loaded, all the unique modules in it are also loaded. The plugin classes override the system classes and so if there is an action that has the same alias name as that of a JIRA action, it is the plugin action class that will be loaded. We will see more about extending actions in the coming chapters.

Suppose you have a report module in your plugin, it will look as follows:

<report key="demo-report" name="My Demo Report" ....>

The plugin key, in this case, will be com.jtricks.demo and the module key will be com.jtricks.demo:demo-report.

Hang on, before you start writing your little plugin for a much wanted feature, have a look at the Atlassian plugin exchange to see if someone else has already done the dirty work for you!

Atlassian plugin exchange

Atlassian plugin exchange is a one stop shop where you can find the entire list of commercial and open source plugins people around the world have written. See https://plugins.atlassian.com/search/by/jira for more details.


A common scenario that people encounter while deploying their plugin is when the plugin fails to load even though everything looks fine. Make sure your plugin's key is unique and is not duplicated in one of yours or another third-party's plugin!

The same applies to individual plugin modules.


Setting up the development environment

Now that we know what a plugin is, let 's aim at writing one! The first step in writing a JIRA plugin is to set up your environment, if you haven't done that already. In this recipe, we will see how to set up a local environment.

To make plugin development easier, Atlassian provides the Atlassian Plugin Software Development Kit (SDK). It comes along with Maven and a pre-configured settings.xml to make things easier.

Atlassian Plugin SDK can be used to develop plugins for other Atlassian products, including Confluence, Crowd, and so on, but we are concentrating only on JIRA.

Getting ready

The following are the pre-requisites for running the Atlassian plugin SDK:

  • The default port for the SDK: 2990 should be available. This is important because different ports are reserved for different Atlassian products.

  • JDK Java version 1.5 - 6 must be installed.

  • Make sure JAVA_HOME is set properly and the command java –version outputs the correct Java version details.

  • And of course, JIRA 4.x+ should be installed in your development environment.


    Make sure you use a context path for your JIRA because there are known issues with the SDK not working when the context path is empty. See https://studio.atlassian.com/browse/AMPS-122 for more details.

How to do it...

  1. Once we have Java installed and the port ready, we can download the latest version of Atlassian Plugin SDK from https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/amps/atlassian-plugin-sdk/.

  2. Unzip the version into a directory of your choice. Let's call this directory SDK_HOME going forward.

  3. Add the SDK's bin directory into the environment PATH variable.

  4. Create a new environment variable M2_HOME pointing to the Apache-Maven directory in your SDK Home.

  5. A lot of commonly used dependencies are already available in the repository folder embedded in the SDK. To use this, edit the settings.xml under M2_HOME/conf/ and modify the localRepository attribute to point to the embedded repository folder. By default, it will use the USER_HOME/.m2/repository.

  6. Install the IDE of your choice. Atlassian recommends Eclipse, IntelliJ IDEA, or NetBeans, as they all support Maven.

  7. Ready, Set, Go…

How it works...

With these steps executed properly, we have a development environment for JIRA plugins.

The next step is to create a Skeleton plugin, import it into your IDE, and start writing some code! Creating the Skeleton plugin, deploying it, and so on, is explained in detail in the following recipes.

There's more...

Even though the aforementioned steps will work in most cases, we will come across scenarios where the setting up of the development environment is not that straightforward. For example, there are extra settings needed for Maven if the machine is behind a firewall. You might even have a local Maven version already installed. In this section, we will see some useful tips on similar cases.

Proxy settings for Maven

If you are behind a firewall, make sure you configure the proxy in the Maven settings.xml file. The proxy can be configured as follows:


Find out more about that and other aspects of Maven at http://maven.apache.org/index.html.

Using local Maven

If you are a developer, in many cases you will have Maven already installed in your local machine. In that case, point M2_HOME to your local Maven and update the respective settings.xml with the repository details in the default settings.xml that ships with Atlassian plugin SDK.

Configuring IDEs to use SDK

If you are using IntelliJ IDEA, it is an easy job because IDEA integrated Maven out-of-the-box. Just load the project by selecting the pom.xml!

If you are using Eclipse, make sure you have M2Eclipse installed. This is because Eclipse integrates Maven through the Sonatype M2Eclipse plugin. You can find more details on configuring this at http://confluence.atlassian.com/display/DEVNET/Configuring+Eclipse+to+use+the+SDK.


If you see Maven download errors like Could not resolve artifact, make sure you verify the following:

  • Entry in Maven settings.xml is correct. That is, it points to the correct repositories

  • Proxy configuration is done if required

  • Antivirus in the local machine is disabled if none of the above works! Seriously, it makes a difference.

See also

  • Creating a skeleton plugin


Creating a skeleton plugin

In this recipe, we will look at creating a skeleton plugin. We will use the Atlassian Plugin SDK to create the skeleton!

Getting ready

Make sure you have the Atlassian Plugin SDK installed and a version of JIRA 4.x running on your local machine.

How to do it...

  1. Open a command window and go to the folder where you want to create the plugin.


    Make sure you use a directory without any spaces because there are known issues with the SDK not working in directories with spaces in it. See https://studio.atlassian.com/browse/AMPS-126 for details.

  2. Type atlas-create-jira-plugin and press Enter.

  3. Enter the groupID when prompted. GroupID would normally be coming from your organization name and mostly resembles the Java package. Of course, you can enter a different package name as we move forward if you want to keep it separate. GroupID will be used to identify your plugin along with artifactId.

    For example: com.jtricks.demo.

  4. Enter the artifactId—the identifier for this artifact. Do not use spaces here.

    For example: demoplugin.

  5. Version—the default version is 1.0-SNAPSHOT. Enter a new version if you want to change it or press Enter to keep the default.

    For example: 1.0

  6. Package—press Enter if the package value is same as the groupID. If not, enter the new value here and press Enter.

    For example, com.jtricks.mypackage

  7. Confirm the selection when prompted. If you want to change any of the entered values, type N and press Enter.

  8. Wait for the BUILD SUCCESSFUL message. You might see a few warnings which can be ignored.

How it works...

A skeleton plugin is nothing but a set of directories and sub directories along with a pom.xml (Maven Project Object Model) file and some sample Java and XML files in the appropriate folders.

Here is a snapshot of how the project will look like in Eclipse. It also shows the design view of the default atlassian-plugin.xml file:

As you can see, there is a pom.xml at the root level and a src folder. A sample LICENSE file and a README file are also created for you at the root level.

Under the src folder, you will find out two folders, main and test, with identical folder structure. All your main Java code goes under the main folder. Any JUnit tests you write will go into the same location under the test folder. There is an additional folder, it, under the test folder where all the integration tests will go!

You will find the plugin descriptor under src/main/resources with sample values already populated in it. The values in the preceding screenshot are populated from the pom.xml. In our case, the plugin key will be populated as com.jtricks.demo:demoplugin when the plugin is built.

There are two more folders under the src/test. src/test/resources, which will hold any resources required for unit tests or integration tests, and the src/test/xml folder can hold the XML data from any other JIRA instance. If the XML is supplied, the SDK will use it to configure the JIRA instance before running the integration tests.

So, that is our plugin Skeleton. All that is pending is some useful Java code and proper module types in the atlassian-plugin.xml file!


Remember, the first Maven run is going to take some time as it downloads all the dependencies into your local repository. A coffee break might not be enough!! If you have a choice, plan your meals. ;)

There's more...

Sometimes, for the geeks, it is much easier to run a single command to create a project without bothering about the step-by-step creation. In this section, we will quickly see how to do it. We will also have a look at how to create an Eclipse project if you opt out of installing m2eclipse.

One step to your skeleton plugin

You can ignore the interactive mode by passing the parameters like groupID, artifactId, and so on, as arguments to the atlas-create-jira-plugin command.

atlas-create-jira-plugin -g my_groupID -a my_artefactId -v my_version -p my_package –non-interactive

In this example, for the values we saw previously, the single line command will be:

atlas-create-jira-plugin -g com.jtricks.demo -a demoplugin -v 1.0 -p com.jtricks.mypackage –non-interactive

You can pick and choose the parameters and provide the rest in an interactive mode as well!

Creating an Eclipse project

If you are not using m2eclipse, just run the following command from the folder where you have the pom.xml file:

atlas-mvn eclipse:eclipse

This will generate the plugin project for Eclipse and you can then import this project into the IDE.

Type atlas-mvn eclipse:clean eclipse:eclipse if you want to clean the old project and create again!

With IDEA or m2eclipse, just opening a file will do. That is, you can just import the project using the option File | Import | Existing Maven Projects, and select the relevant project.

See also

  • Deploying a plugin

  • Making changes and re-deploying a plugin


Deploying a plugin

In this recipe, we will see how to deploy a plugin into JIRA. We will see both the automated deployment using Atlassian Plugin SDK and the manual deployment.

Getting ready

Make sure you have the development environment set up, as we discussed earlier. Also the skeleton plugin should now have the plugin logic implemented in it.

How to do it...

Installing a JIRA plugin using Atlassian Plugin SDK is a cake walk. Here is how it is done:

  1. Open a command window and go to your plugin's root folder, that is, the folder where your pom.xml resides.

  2. Type atlas-run and press Enter. It is possible to pass more options as argument to this command for which the details can be found at: http://confluence.atlassian.com/display/DEVNET/atlas-run.

  3. You will see a lot of things happening as Maven downloads all the dependent libraries into your local repository. As usual, it is going to take lot of time when you run it for the first time.

  4. If you are on Windows, and if you see a security alert popping up, click on Unblock to allow incoming network connections.

  5. When the installation is completed, you will see the following message:

    [WARNING] [talledLocalContainer] INFO: Server startup in 123558 ms
    [INFO] [talledLocalContainer] Tomcat 6.x started on port [2990]
    [INFO] jira started successfully and available at http://localhost:2990/jira
    [INFO] Type CTRL-C to exit
  6. Open http://localhost:2990/jira in your browser.

  7. Login using the username as admin and password as admin.

  8. Test your plugin! You can always go to the Administration | Plugin menu to confirm that the plugin is deployed properly.

If you already have a local JIRA installed or if you want to manually install your plugin for some reason, all you need to do is to package the plugin JAR and copy it across to the JIRA_Home/plugins/installed-plugins directory.

You can package the plugin using the following command:

atlas-mvn clean package

Use atlas-mvn clean install if you also want to install the package plugin into your local repository.

How it works...

There is only one single command that does the whole thing: atlas-run. When you execute this command, it does the following:

  1. Builds your plugin JAR file

  2. Downloads the latest/specified version of JIRA to your local machine if it is the first time you're running the command.

  3. Creates a virtual JIRA installation under your plugin/target folder.

  4. Copies the JAR file into the /target/jira/home/plugins/installed-plugins directory

  5. Starts JIRA in the Tomcat container.

Now, if you look at your target folder, you will see a lot of new folders which were created for the virtual JIRA installation! The two main folders are the container folder, which has the Tomcat container setup, and the jira folder, which has the JIRA WAR along with the JIRA home setup!

You will find the database (HSQLDB), indexes, backups, and attachments under /target/jira/home. And you will see your jira-webapp at /target/container/tomcat6x/cargo-jira-home/webapps/jira.

If you have any JSPs that need to be put under the webapp, you will have to copy it to the appropriate folder under the aforementioned path!

There's more...

There's more to this.

Using a specific version of JIRA

As mentioned earlier, atlas-run deploys the latest version of JIRA. But what if you want to deploy the plugin into an earlier version of JIRA and test it?

There are two ways to do it:

  1. Mention the JIRA version as an argument to atlas-run; make sure you run atlas-clean, if you already have the latest version deployed:

    • Run atlas-clean (if required).

    • Run atlas-run –v 4.1.2 or atlas-run –version 4.1.2 if you are developing for JIRA version 4.1.2. Replace the version number with a version of your choice.

  2. Permanently change the JIRA version in your plugin pom.xml:

    • Go to your pom.xml.

    • Modify the jira.version property value to the desired version.

    • Modify the jira.data.version to a matching version.

This is how it will look for JIRA 4.1.2:


Reusing the configurations in each run

Suppose you added some data on to virtual JIRA, how do you retain it when you clean start-up JIRA next time?

This is where a new SDK command comes to our rescue.

After the atlas-run is finished, that is, after you pressed Ctrl + C, execute the following command:


This will generate a file named generated-test-resources.zip under the target folder. Copy this file to the /src/test/resources folder or any other known locations. Now modify the pom.xml to add the following entry under configurations in the maven-jira-plugin:


Modify the path accordingly. This will reuse the configurations the next time you run atlas-run.


  • Missing JAR file exception? Make sure the local-repository attribute in the settings.xml file points to the embedded Maven repository that comes with the SDK. If the problem still persists, manually download the missing JAR files and use atlas-mvn install to install them in to the local repository.

    Watch out for the proxy settings or antivirus settings that can potentially block the download in some cases!

  • BeanCreationException? Make sure your plugin is of version 2. Check your atlassian-plugin.xml to see if the following entry is there or not. If not, add the entry:

    <atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${project.artifactId}" plugins-version="2">

Run atlas-clean followed by atlas-run after you do that.


Making changes and re-deploying a plugin

Now that we have deployed the test plugin, it is time to add some proper logic, re-deploy the plugin, and test it. Making the changes and re-deploying a plugin is pretty easy. In this recipe, we will quickly look at how to do this.

How to do it...

You can make changes to the plugin and re-deploy it while the JIRA application is still running. Here is how we do it:

  1. Keep the JIRA application running in the window where we ran atlas-run.

  2. Open a new command window and go to the root plugin folder where your pom.xml resides.

  3. Run atlas-cli.

  4. Wait for the command—Waiting for messages.

  5. Run pi. Pi stands for "plugin install" and this will compile your changes, package the plugin JAR, and install it into the installed-plugins folder.

Now, there is one thing you need to keep an eye on! Not all the plugin modules can be redeployed like this prior to JIRA 4.4. The following is a list of the plugin modules that can be reloaded with pi in JIRA 4.0.x:

  • ComponentImport

  • Gadget

  • ModuleType

  • Resource

  • REST

  • ServletContextListener

  • ServletContextParameter

  • ServletFilter

  • Servlet

  • WebItem

  • WebResource

  • WebSection

If your plugin module is not there in the preceding list or if the changes doesn't seem to be reflected, press Ctrl + C in the command window running atlas-run and re-run the atlas-run command. That will re-deploy the plugin and restart JIRA.

Post JIRA 4.1, SDK supports reloading of more modules, but whether it works or not depends on what the module does internally.

JIRA 4.4+ supports reloading of all the plugin modules.

Debugging in Eclipse

It is also possible to run the plugin in debug mode and point your IDE's remote debugger to it.

Following are the steps to do this in Eclipse:

  1. Use atlas-debug instead of atlas-run.

  2. Once the virtual JIRA is up and running with tour plugin deployed in it, go to Run | Debug Configurations in Eclipse.

  3. Create a new Remote Java Application.

  4. Give a name, keep the defaults, and give the port number as 5005. This is the default debug port on which the virtual JIRA runs.

  5. Happy Debugging!

See also

  • Setting up the development environment

  • Creating a skeleton plugin


Testing and debugging

In the world of Test Driven Development (TDD), writing tests is a part and parcel of the development process. I don't want to bore you with why testing is important! Let us just say, all these holds true for JIRA plugin development as well.

In this recipe, we will see the various commands for running unit tests and integration tests in JIRA plugins.

Getting ready

Make sure you have the plugin development environment set up and the skeleton plugin created!

You might have noticed that there are two sample test files, one each for unit tests and integration tests, created under the src/test/java/your_package/ and src/test/java/it folders.

Once you have it ready, it is time to write some tests and run those tests to make sure things work as expected!

How to do it...

The first step is to write some tests! We recommend you to use some powerful testing frameworks like JUnit in collaboration with mocking frameworks like PowerMock or Mockito. Make sure you have the valid dependencies added on to your pom.xml.

Let us now make a huge assumption that you have written a few tests!

Following is the command to run your unit tests from the command line:


The normal Maven command atlas-mvn clean test also does the same thing. If you are running the integration tests, the command to use is:


Or the Maven command: atlas-mvn clean integration-test.

Once we are on to the stage of running tests, we will see it failing at times. There comes the need for debugging. Checkout the *.txt and *.xml files created under target/ surefire-reports/ which has all the required information on the various tests that are executed.

Now, if you want to skip the tests at the various stages, use –skip-tests. For example, atlas-unit-test --skip-tests will skip the unit tests.

You can also use the Maven options directly to skip the unit/integrations tests or both together.

  • -Dmaven.test.skip=true: skips both unit and integration tests

  • -Dmaven.test.unit.skip=true: skips unit tests

  • -Dmaven.test.it.skip=true: skips integration tests

How it works...

The atlas-unit-test command merely runs the related Maven command: atlas-mvn clean test in the backend to execute the various unit tests. It also generates the outputs into the surefire-reports directory for reference or debugging.

The atlas-integration-test does a bit more. It runs the integration tests in a virtual JIRA environment. It will start up a new JIRA instance running inside a Tomcat container, set up the instance with some default data including a temporary license that lasts for three hours, and execute your tests!

How does JIRA differentiate between the unit tests and integration tests? This is where the folder structure plays an important role. Anything under the src/test/java/it/ folder will be treated as integration tests and everything else will be treated as unit tests!

There's more...

There is more to it.

Using custom data for Integration/Functional Tests

While atlas-integration-test makes our life easier by setting up a JIRA instance with some default data in it, we might need some custom data as well to successfully run a few functional tests.

We can do this in a couple of steps:

  1. Export the data from a pre-configured JIRA instance into XML.

  2. Put it under the src/test/xml/ directory.

  3. Provide this path as the value for the jira.xml.data.location property in the localtest.properties under src/main/resources.

The XML resource will then be imported to JIRA before the tests are executed.

Testing against different version of JIRA/Tomcat

Just like the atlas-run command, you can use the -v option to test your plugin against a different version of JIRA. As before, make sure you do an atlas-clean before running the tests if you had tested it against another version before.

You can also use the -c option to test it against a different version of the Tomcat container.

For example, atlas-clean && atlas-integration-test -v 3.0.1 -c tomcat5x will test your plugin against JIRA version 3.0.1 using Tomcat container 5.

See also

  • Setting up the development environment

  • Deploying a plugin

About the Authors
  • Jobin Kuruvilla

    Jobin Kuruvilla is an Atlassian Consultant with experience in customizing JIRA and writing JIRA plugins for various customers. He is currently working with Go2Group as an Atlassian platinum expert, and is involved in managing Atlassian products for big enterprises as well as small starter license installations. Jobin is the author of JIRA Development Cookbook, Packt Publishing, released in 2011, which is a well-received book in the JIRA community. He also runs a website named J-Tricks (http://www.j-tricks.com), using which he shares numerous tutorials to help the developer community, who he believes have contributed immensely to his personal development. It is indeed those tutorials that sowed the first seeds of JIRA Development Cookbook. Jobin started his career as a Java/J2EE developer in one of the biggest IT companies in India. After spending his initial years in the SOA world, he got hooked into this amazing product called JIRA, which he came across during the evaluation of a number of third-party tools. Soon, Jobin realized the power of JIRA, and pledged to spread the word. He has been doing it ever since, and he reckons there is a long way to go!

    Browse publications by this author
  • Jobin Kuruvilla

    Jobin Kuruvilla is an Atlassian Consultant with experience in customizing JIRA and writing JIRA plugins for various customers. He is currently working with Go2Group as an Atlassian platinum expert, and is involved in managing Atlassian products for big enterprises as well as small starter license installations. From an IT nerd to a DevOps evangelist, Jobin has performed various roles in his professional journey so far. Jobin is the author of JIRA Development Cookbook, released in 2011, and JIRA 5.x Development Cookbook, released in 2013, both published by Packt Publishing and well-received in the JIRA community. He also runs a website named J-Tricks (http://www.j-tricks.com), using which he shares numerous tutorials to help the developer community, who he believes have contributed immensely to his personal development. It is indeed those tutorials that sowed the first seeds of JIRA Development Cookbook. Jobin started his career as a Java/J2EE developer in one of the biggest IT companies in India. After spending his initial years in the SOA world, he got hooked into this amazing product called JIRA, which he came across during the evaluation of a number of third-party tools. Soon, Jobin realized the power of JIRA, and pledged to spread the word. He has been doing it ever since, and he reckons there is a long way to go! Outside the office, Jobin enjoys sports, especially soccer, and is on the verge of getting addicted to movies and social networking sites. Acknowledgment: No book is the product of just the author; he just happens to be the one with his name on the cover. A number of people contributed to the success of this book, and it would take more space than I have to thank each one individually. First of all, thanks to the Almighty God for helping me to sail through the difficulties in this short life and for making my life as wonderful as it is now. The next biggest thanks goes to the Content Development Editor, Samantha Gonsalves, and Acquisition Editor, Prachi Bisht, both of whom went through the pain of making me write another book. Also, thanks to the entire Packt Publishing team for working so diligently to help bring out another high quality product. It is amazing to work with talented developers and technical geeks. Thank you to all the intelligent minds, with whom I got a chance to share this amazing journey of programming. Your encouragement and support were/are invaluable to me; you guys rock! I must also thank the talented Atlassian community who are instrumental in helping each other, sharing solutions, being active in the forums, running user groups, and whatnot. I am just one of the many who have benefited. Before I wind up, thank you Atlassian for giving us JIRA and a set of other wonderful products. You don't realize how much you are making our lives easier. Go Team! Last, but not the least, a big thanks to all at Go2group for the support extended in writing this book and believing in my capabilities. We will, together, continue to simplify complexities for our numerous customers.

    Browse publications by this author
JIRA Development Cookbook
Unlock this book and the full library FREE for 7 days
Start now