<![CDATA[J tricks - Little JIRA Tricks - Tutorials]]>Wed, 15 Apr 2026 14:30:06 -0400Weebly<![CDATA[JIRA Development Cookbook - Third Edition is officially published]]>Tue, 11 Oct 2016 16:10:01 GMThttps://www.j-tricks.com/tutorials/jira-development-cookbook-third-edition-is-officially-publishedToday is the first day of Atlassian Summit 2016. Excited about the upcoming announcements of awesome features and unexpected goodies? I am!

To add to the excitement, here is a humble gift. JIRA Development Cookbook - Third Edition is now officially published.

Picture

The book is available for purchase at Packt website and Amazon.

Packt: https://www.packtpub.com/application-development/jira-development-cookbook-third-edition
Amazon: https://www.amazon.com/Jira-7-Development-Cookbook-Third/dp/1785885618

If you are interested in customizing your best project management software, JIRA, to unleash its full potential, grab your copy now!

Hope you like it and I am excited to hear from you.

PS: If you are at Summit, I invite you to meet me at the Go2Group booth. Talk to you soon!

Jobin Kuruvilla,
Author - JIRA Development Cookbook series
]]><![CDATA[JIRA Development Cookbook - Third Edition. Coming soon..]]>Fri, 26 Aug 2016 02:16:34 GMThttps://www.j-tricks.com/tutorials/jira-development-cookbook-third-edition-coming-soonThe wait is almost over!
Picture
Watch this space..
]]><![CDATA[JIRA Development Cookbook(s) on sale!]]>Sat, 12 Mar 2016 15:44:37 GMThttps://www.j-tricks.com/tutorials/jira-development-cookbooks-on-saleWhile we wait for the impending release of the next version of JIRA Development Cookbook, here is something to cheer you up.

JIRA Development Cookbook eBook(s) are on SALE!

Picture

Use the code JIRA500DEV while you order the the JIRA Development Cookbook eBook or the JIRA Development 5.x Development Cookbook eBook in the Packt website.

Stay tuned for more news on the release of the next version of the JIRA Development Cookbook. Happy coding!
]]><![CDATA[Atlassian Spring Scanner and NoSuchBeanDefinitionException]]>Wed, 27 Jan 2016 01:52:13 GMThttps://www.j-tricks.com/tutorials/atlassian-spring-scanner-and-nosuchbeandefinitionexceptionNoSuchBeanDefinitionException is a notorious exception in the JIRA Development world. Some even have had nightmares about it I hear!

But then, this is a well documented error and even we have attempted documenting it here - to save hours of debugging and, of course, to provide a good night's sleep!!

With the latest Atlassian Plugin SDK though, it seems the nightmares are back. And I have seen a rising number of questions about this error in Atlassian Answers and other forums. Are you one of those who ran into the same? If so, don't blame it on Atlassian or the plugin SDK. You are just ignorant, as I was for a good few hours, about the Atlassian Spring Scanner libraries.

"Atlassian Spring Scanner is a set of libraries that make plugins faster to load and easier to develop.". It scans the source code to find special annotations and creates special index files in the JAR's META-INF directory. These index files are read at runtime to create the necessary Spring components and OSGI services.

What does it mean though?

Once you have the spring scanner plugin, and related dependencies, added in the pom.xml, it will not look for component definitions in the atlassian-plugin.xml and will, instead, look for scanner annotations. Even the dependency injection requires the special annotations in the code.

And yes, spring scanner plugin is enabled by default in the pom.xml when you create the plugin skeleton, by running atlas-create-jira-plugin, using the latest plugin SDK. That means you will run into NoSuchBeanDefinitionException when you inject components in the constructor without using the required annotations. Or when you use component-import definitions inside the atlassian-plugin.xml. Or when you use public="true" to export one of your components. And so on..

For example, let is create a simple skeleton plugin using the new Plugin SDK (6.1.2 as of now) and add a webwork module definition.

<webwork1 key="plugin-scanner-action" name="Plugin Scanner Action" i18n-name-key="plugin-scanner-action.name">
    <description key="plugin-scanner-action.description">Demos how the scanner annotations work</description>
    <actions>
      <action name="com.jtricks.jira.webwork.PluginScannerDemo" alias="PluginScannerDemo">
        <view name="success">/templates/plugin-scanner-action/pluginscannerdemo/success.vm</view>
      </action>
    </actions>
</webwork1>

In the action class, we can keep it simple by injecting the ever popular JiraAuthenticationContext interface, as shown below:

public class PluginScannerDemo extends JiraWebActionSupport {
    private static final Logger log = LoggerFactory.getLogger(PluginScannerDemo.class);

    private final JiraAuthenticationContext authContext;

    private String currentUser;

    public PluginScannerDemo(JiraAuthenticationContext authContext) {
        super();
        this.authContext = authContext;
    }

    @Override
    protected String doExecute() throws Exception {
        if (this.authContext.getLoggedInUser() != null) {
            this.currentUser = this.authContext.getLoggedInUser().getDisplayName();
        } else {
            this.currentUser = "Anonymous";
        }
        return super.doExecute();
    }

    public String getCurrentUser() {
        return currentUser;
    }
}

And we can create a success view that prints the currentUser.

<h1>Welcome $!currentUser!</h1>

It looks very simple but you will run into the, you guessed it right, NoSuchBeanDefinitionException when this code is executed.

[INFO] [talledLocalContainer] 2016-01-26 10:52:19,659 http-nio-2990-exec-7 ERROR admin 652x237x3 zb3hwx 0:0:0:0:0:0:0:1 /secure/PluginScannerDemo.jspa [c.a.j.web.dispatcher.JiraWebworkActionDispatcher] Exception thrown from action 'PluginScannerDemo', returning 404
[INFO] [talledLocalContainer] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.jtricks.jira.webwork.PluginScannerDemo': Unsatisfied dependency expressed through constructor argument with index 0 of type [com.atlassian.jira.security.JiraAuthenticationContext]: : No qualifying bean of type [com.atlassian.jira.security.JiraAuthenticationContext] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [com.atlassian.jira.security.JiraAuthenticationContext] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {}

We know that JiraAuthenticationContext is a public component and doesn't need a component-import definition. Even if we add it in the atlassian-plugin.xml, as described in one of our earlier tips, that is not going to help with this error.

This is where we need to start adding the new scanner annotations. Following are the important ones.
  • @ExportAsService: Replaces <component ... public="true"> and exposes the class as a OSGi service.
  • @Named (JSR) or @Component (Spring): Replaces <component ...> definition.
  • @Autowired or @Inject: Used for dependency injection
  • @ComponentImport: Replaces <component-import ...> definition.
  • @ClasspathComponent: Defined a component whose class is contained in some other library.
  • @ModuleType: Replaces <module-type.. > definition.

And you will find more annotations and finer details at https://bitbucket.org/atlassian/atlassian-spring-scanner.

Our modified code, with all these annotations, will look like this:

@Named ("PluginScannerDemo")
public class PluginScannerDemo extends JiraWebActionSupport {
    private static final Logger log = LoggerFactory.getLogger(PluginScannerDemo.class);

    @ComponentImport
    private final JiraAuthenticationContext authContext;

    private String currentUser;

    @Inject
    public PluginScannerDemo(JiraAuthenticationContext authContext) {
        super();
        this.authContext = authContext;
    }

    @Override
    protected String doExecute() throws Exception {
        if (this.authContext.getLoggedInUser() != null) {
            this.currentUser = this.authContext.getLoggedInUser().getDisplayName();
        } else {
            this.currentUser = "Anonymous";
        }
        return super.doExecute();
    }

    public String getCurrentUser() {
        return currentUser;
    }
}

And, voilà, Everything works as expected!

You can find the full code attached at the end of this blog.

But, if you want to stick with old style, maybe because you are upgrading a huge plugin, you can do that by removing the Spring Scanner plugin and its dependencies from the pom.xml. As simple as that! You can find the source code, for the above example, without the spring scanner attached as plugin-scanner-demo-old-style.zip.

Note that Spring Scanner is recommended because the code with annotations load significantly faster than traditional P2 plugins that require runtime transformation. As per Atlassian, local tests show plugins that took 5 seconds to load now load in under 2 seconds. Being more explicit about the code, using annotations, is indeed a fair trade-off, if that is the case.

Hope you enjoyed this tip. You can read more such tips in the new version of JIRA Development Cookbook, that is coming out soon. Stay tuned!
plugin-scanner-demo.zip
File Size: 21 kb
File Type: zip
Download File
plugin-scanner-demo-old-style.zip
File Size: 21 kb
File Type: zip
Download File
]]><![CDATA[JIRA Development Cookbook - What's next?]]>Sat, 12 Dec 2015 17:47:59 GMThttps://www.j-tricks.com/tutorials/jira-development-cookbook-whats-next
Picture
]]><![CDATA[Setting formatted dates using javascript in JIRA]]>Sat, 10 May 2014 13:32:10 GMThttps://www.j-tricks.com/tutorials/setting-formatted-dates-using-javascript-in-jiraWow, it's been a while since the last post. Crazy schedule but this one is too cool to ignore!

Did you ever want to populate a date field in JIRA but with all the formatting defined in JIRA itself? And maybe add, subtract days etc using javascript?

Well, it is easier than you think. And no need to write crazy javascript code to do all the calculations by yourself. Just offload the work to Moment.js! And that is exactly what JIRA does, thanks to Wojciech Urbanski from Atlassian for pointing that out in this post.

For example, if you want to set the current date to "due date" in an issue, you can use this:

var due = moment(new Date());
var dateString = due.format(JIRA.translateSimpleDateFormat(AJS.Meta.get("date-dmy")));
AJS.$('#duedate').val(dateString);

That's all!

How about if you want to set the due date 5 days from now? It is again Moment.js that comes to the rescue.

var due = moment().add('days', 5);
var dateString = due.format(JIRA.translateSimpleDateFormat(AJS.Meta.get("date-dmy")));
AJS.$('#duedate').val(dateString);

What about setting the date and time on a datetime custom field instead of just the date? Use date-complete instead of date-dmy.

var due = moment(new Date());
var dateString = due.format(JIRA.translateSimpleDateFormat(AJS.Meta.get("date-complete")));
AJS.$('#duedate').val(dateString);

You can find the other available formats at atlassian-jira/includes/jquery/plugins/livestamp/moment.jira.i18n.js. Or checkout the page source for more such attributes that can be retrieved via AJS.Meta.get().

Yup, that is what I thought. Cool stuff!
]]><![CDATA[JIRA notification messages]]>Sun, 08 Dec 2013 16:49:54 GMThttps://www.j-tricks.com/tutorials/jira-notification-messagesEver wondered how the nice little JIRA notification messages are created? The ones you get when an issue is created in JIRA?
Picture
Doing this is so easy that you will want to try it out in every new plugin that you write!

All you need is to inject the following javascript snippet into the page:

JIRA.Messages.showSuccessMsg('Your message goes here');

Let me show you a simple demonstration of this. I am going to put this into the announcement banner so that I don't have to create a plugin to inject this javascript ;)

Let us say we need to show this message when a user visits the profile. All you need to do is to add this snippet in the Announcement banner.

<script >
var pathname = window.location.pathname;
if (pathname.indexOf("ViewProfile.jspa") >= 0)
{
   JIRA.Messages.showSuccessMsg('You are viewing your profile, Success');
}
</script>

And the message will appear on the screen when you visit the profile.
Picture
But, did you notice that the message didn't have a close button as you normally see in the Create notification? This is where you can pass properties to the function.

<script >
var pathname = window.location.pathname;
if (pathname.indexOf("ViewProfile.jspa") >= 0)
{
   JIRA.Messages.showSuccessMsg('You are viewing your profile', {closeable: true});
}
</script>

Here we passed the closeable property to the same function and the message will now have a close option.
Picture
Now, you can replace the showSuccessMsg function with showErrorMsg or showWarningMsg to get the appropriate message format.
Picture
ERROR
Picture
WARNING
In all the 3 cases, the message disappears itself after the default timeout of 10 seconds. If you need a bigger timeout, use the timeout property.

<script >
var pathname = window.location.pathname;
if (pathname.indexOf("ViewProfile.jspa") >= 0)
{
   JIRA.Messages.showSuccessMsg('You are viewing your profile', {closeable: true, timeout: 60});
}
</script>

Are there any other properties? The only other property is type and you can use it when you use the generic function showMsg instead of showSuccessMsg, showErrorMsg or showWarningMsg. The possible type values are SUCCESS, ERROR or WARNING.

For example:

JIRA.Messages.showSuccessMsg('You are viewing your profile', {closeable: true, timeout: 60});

is same as

JIRA.Messages.showMsg('You are viewing your profile', {type: SUCCESS, closeable: true, timeout: 60});

For more details on how these functions work and for more more useful functions like showReloadSuccessMsg, take a look at includes/jira/common/messages.js file. Hope you find it useful.

PS: If you find these little tutorials useful, you might also like the JIRA Development Cookbook.
]]><![CDATA[Date, DateTime and User picker fields]]>Sun, 03 Nov 2013 01:31:08 GMThttps://www.j-tricks.com/tutorials/date-datetime-and-user-picker-fieldsWith the evolution of JIRA over the years, it has a set of nice APIs or helper methods for doing pretty much everything. But one thing that I always have to look up while developing plugins is using date and user pickers in a velocity template.

As usual, it is something that is really easy once you look it up. Here is a simplified version of what I have done in the last few versions of JIRA.

Let us create a sample plugin with a simple webwork action. How about an alias of Picker? Is there a more obvious name to call this example? ;)

  <webwork1 key="picker-module" name="PickerModule" i18n-name-key="picker-module.name">
    <description key="picker-module.description">Sample date and user picker in velocity templates</description>
    <actions>
      <action name="com.jtricks.jira.webwork.Picker" alias="Picker">
        <view name="success">/templates/picker-module/picker/success.vm</view>
      </action>
    </actions>
  </webwork1>

As you can see, we just have a simple webwork actions and a velocity template associated with the success view. All we are going to do here is to create a form in the view with sample picker fields. I have generalized methods so that you can use it for as many picker fields as you want on the same page.

Date Picker field

Really easy to do this! Couple of steps:

1. Add this macro in the beginning of the template.

  #macro(datePopup $inputId $inputButton $dateFormat)
  <script language="javascript" >
       Calendar.setup({
                firstDay : 1,
                inputField : '$inputId',
                button : '$inputButton',
                align : 'Br',
                singleClick : true,
                showsTime : false,
                useISO8601WeekNumbers : false,
                ifFormat : '$dateFormat'
       });
   </script>
   #end

2. Use the macro in the field group as shown below:

   <div >
         <label for="uniqueDateId">Date Field Name</label>
         <input id="uniqueDateId" name="name" />
         <a href="#" id="uniqueDateId_trigger" title="Enter your date field">
               <span ></span>
         </a>
         #datePopup("uniqueDateId" "uniqueDateId_trigger" $dateFormat)
    </div>

That's it! 

As you can see, the input field has a unique id (uniqueDateId in this example) and the anchor tag has a matching id which of the format ${id_of_input_field}_trigger (uniqueDateId_trigger in this example). Make sure pass this input field Id and anchor id to the datePopup macro we created in step 1.

The result is what you can see here:
Picture


DateTime Picker field

This is much similar to Date field, except for the number of arguments passed to the macro. It takes a date time format and a time format as opposed to the date format. Following are the steps:

1. Add a macro similar to what we did earlier.

   #macro(dateTimePopup $inputId $inputButton $dateTimeFormat $timeFormat)
   <script language="javascript" >
              Calendar.setup({
                         firstDay : 1,
                         inputField : '$inputId',
                         button : '$inputButton',
                         align : 'Br',
                         singleClick : true,
                         showsTime : true,
                         useISO8601WeekNumbers : false,
                         ifFormat : '$dateTimeFormat',
                         timeFormat : '$timeFormat'
               });
     </script>
     #end

The main difference is the formats. In the script, ifFormat uses a date time format instead of date format. There is also a timeFormat argument. Also showsTime argument is true instead of false.

2. Use the macro similar to what we did for datePopup. The unique ids should be just like what we did there.

   <div >
         <label for="uniqueDateTimeId">DateTime Field Name</label>
         <input id="uniqueDateTimeId" name="name" />
         <a href="#" id="uniqueDateTimeId_trigger" title="Enter your date time field">
                <span ></span>
         </a>
         #dateTimePopup("uniqueDateTimeId" "uniqueDateTimeId_trigger" $dateTimeFormat $timeFormat)
    </div>

Unique input id is uniqueDateTimeId and anchor id is uniqueDateTimeId_trigger. Here is how the field will appear on screen:
Picture

User Picker field

User picker is slightly different. Here we make use of JIRA's user picker browser where you can search for users based on name, email or group. 

In the page, we click on the user picker icon to open up the user picker browser as a popup window and when you click on the search result, it fills the form back with the result selected.

Steps are as follows:

1. Add a javascript function that opens up the user picker

   <script language="javascript" >
         function openUserPickerWindow(element){
            var vWinUsers = window.open('$!requestContext.canonicalBaseUrl/secure/popups/UserPickerBrowser.jspa?formName=jiraform&multiSelect=false&element=' + element, 'UserPicker', 'status=yes,resizable=yes,top=100,left=200,width=580,height=750,scrollbars=yes');
            vWinUsers.opener = self;
            vWinUsers.focus();    
         }
    </script>

The openUserPickerWindow method just opens up a user picker browser popup with the element attribute as the source input id (element variable). Note that the formName in the example is jiraform and change it as appropriate.

2. Invoke the function when you click on the user picker icon.

    <div >
          <label for="uniqueUserId">User Field Name</label>
          <input id="uniqueUserId" name="lead"/>
          <a href="javascript:openUserPickerWindow('uniqueUserId');">
               <img title="Ente the user name" name="multiuserImage" src="$!requestContext.canonicalBaseUrl/images/icons/filter_public.gif" hspace="0" height="16" width="16" border="0" align="absmiddle" >
          </a>
      </div>

Here also the input field has a unique id (uniqueUserId in the example) and that is passed in the anchor tag. You can change the icon as you want in the image tag.

Once added, the field appears on the form like this:
Picture

When you click on the user browser icon, it opens up the popup as shown below:
Picture

When you click on the 'admin' row, uniqueUserId on the form is populated as shown.
Picture

Yeah right, you have seen it a lot in JIRA ;)

The example code is uploaded at the end of the tutorial and you can run the webwork action using the URL http://localhost:2990/jira/secure/Picker.jspa.

That's all. 3 simple pickers, easy steps. How about the Ajax user search? Well, some other day :P

picker-plugin.zip
File Size: 30 kb
File Type: zip
Download File
]]><![CDATA[Component [Import] Gotchas - NoSuchBeanDefinitionException]]>Mon, 15 Jul 2013 03:37:21 GMThttps://www.j-tricks.com/tutorials/component-import-gotchas-nosuchbeandefinitionexceptionEver since Plugins 2.0 was introduced, I have come across the NoSuchBeanDefinitionException more than anything else.

And this happens when you try to inject a JIRA component in the constructor. Following is a typical example.

[INFO] [talledLocalContainer] Caused by: org.osgi.framework.BundleException: Unresolved constraint in bundle com.jtricks.component-tricks-tests [105]: Unable to resolve 105.0: missing requirement [105.0] package; (package=com.jtricks)
[INFO] [talledLocalContainer]     at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409)
[INFO] [talledLocalContainer]     at org.apache.felix.framework.Felix.startBundle(Felix.java:1709)
[INFO] [talledLocalContainer]     at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:905)
[INFO] [talledLocalContainer]     at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:892)
[INFO] [talledLocalContainer]     at com.atlassian.plugin.osgi.factory.OsgiPlugin.enableInternal(OsgiPlugin.java:417)
[INFO] [talledLocalContainer]     ... 53 more
[INFO] [talledLocalContainer] Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.atlassian.sal.api.user.UserManager] is defined: Unsatisfied dependency of type [interface com.atlassian.sal.api.user.UserManager]: expected at least 1 matching bean
[INFO] [talledLocalContainer]     at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:613)
[INFO] [talledLocalContainer]     at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:622)
[INFO] [talledLocalContainer]     at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:584)

Fortunately, the fix is a simple one. Atlassian gives the component-import plugin module. For the above error, all you need to do is to add the following in the atlassian-plugin.xml file.

<component-import key="userManager" interface="com.atlassian.sal.api.user.UserManager"/>

You would imagine the same will work for every component, Wouldn't you? Unfortunately, that is not the case!

Here is an example: JiraDurationUtils.

[INFO] [talledLocalContainer] Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.atlassian.jira.util.JiraDurationUtils] is defined: Unsatisfied dependency of type [class com.atlassian.jira.util.JiraDurationUtils]: expected at least 1 matching bean
[INFO] [talledLocalContainer]     at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:613)

Naturally, one would add the component-import tag for the class. I added the following:

<component-import key="jiraDurationUtils" interface="com.atlassian.jira.util.JiraDurationUtils" />

This fixed the above error but along came another!

[INFO] [talledLocalContainer] 2013-07-12 00:11:44,650 pool-5-thread-3 ERROR admin 11x1420x1 xq2dkb 127.0.0.1 /rest/plugins/1.0/ [plugin.osgi.factory.OsgiPlugin] Never resolved service '&jiraDurationUtils' for plugin 'com.jtricks.component-tricks' with filter (object.atlassian.jira.util.JiraDurationUtils)

So, how is JiraDurationUtils different from other components? If you look at the JIRA source, ContainerRegistrar class to be exact, you will see that the JiraDurationUtils component is registered as an internal class.

register.implementation(INTERNAL, JiraDurationUtils.class);

And that is exactly what causes the new exception.

Fortunately, the fix is again an easy one. Instead of using component-import in this case, assume JiraDurationUtils as a class in your plugin (which is of course imported via jira-api dependency). To make it available for constructor injection, define the class as a component in the atlassian-plugin.xml. Int this case, the definition will be as follows:

<component key="jiraDurationUtils" name="JIRA Duration Utils" class="com.atlassian.jira.util.JiraDurationUtils">
</component>

That's all. Everything will work fine and you don't need the component-import anymore.

Want another example? Take ComponentLocator interface. Instead of

<component-import key="componentLocator" interface="com.atlassian.jira.util.ComponentLocator" />

you will end up adding the following:

<component key="componentLocator" name="Component Locator" class="com.atlassian.jira.util.JiraComponentLocator">
        <interface>com.atlassian.jira.util.ComponentLocator</interface>
</component>

Attached is a sample listener code for you to try it out. Till the next one, enjoy the recipes in JIRA 5.x Development cookbook ;)
component-tricks.zip
File Size: 16 kb
File Type: zip
Download File
]]><![CDATA[Win A Free Copy of Packt's JIRA 5.x Development Cookbook!!]]>Tue, 11 Jun 2013 02:40:48 GMThttps://www.j-tricks.com/tutorials/win-a-free-copy-of-packts-jira-5x-development-cookbookWe are pleased to announce that we are organizing a giveaway especially for you. All you need to do is just comment below the post and win a free copy of JIRA 5.x Development Cookbook.

Two lucky winners stand a chance to win copy of the book. Keep reading to find out how you can be one of the Lucky One.
Picture

Overview of JIRA 5.x Development Cookbook
  • Extend and customize JIRA; work with custom fields, workflows, reports, gadgets, JQL functions, plugins, and more
  • Customize the look and feel of your JIRA user interface by adding new tabs, web items and sections, drop down menus, and more
  • Master JQL (JIRA Query Language) that enables advanced searching capabilities through which users can search for issues in their JIRA instance and then exploit all the capabilities of the issue navigator

How to Enter?

Simply post your expectations from this book in comments section below. You could be one of the 2 lucky participants to win the copy.

DeadLine

The contest will close on 10th July 2013, a month from today. Winners will be contacted by email, so be sure to use your real email address when you comment!

Note from Packt:

Winners residing only in the USA and Europe would get a chance to win print copies. Others would be provided with eBook copies.

Is it worth it?

Maybe ;) Listen to couple of reviews on JIRA Development Cookbook!
"Jobin Kuruvilla, an experienced JIRA consultant and plugin developer, set out on the ambitious task to write a detailed and thorough book about JIRA plugin development. The result? A well crafted 450+ page book that starts by introducing the reader to Atlassian’s plugin framework and ends with useful recipes usually gained only by weathered experience. It’s a great read for Atlassian plugin developers at all levels."

Read More...
"I felt compelled to write a review of this book because I think it deserves it, it's a must-have for a JIRA plugin programmer. Before writing this, I thought I'd write a more in-depth review. Surprisingly, I discovered that enumerating each and every subject this book covers was not necessary: it's a homogeneous, extensive and well organized book.
From a developer standpoint, it's an effective and efficient mean to learn the subject and get the job done, much better than any tutorial I've seen so far. Together with the official Atlassian JIRA documentation, this book is pretty much all you need."

Read More...
So, there it is! Grab this chance and become a proud owner of JIRA 5.x Development Cookbook. And don't forget to review the same so that we can make it even better in the next edition!

And, if you can't wait a month, order your copy today at Amazon or Packt website.
]]>