I am sure most of you would know what a JIRA workflow is. And most of you would have custom workflows implemented in your JIRA instance - for good or bad!
And while maintaining those workflows you certainly would have used the JIRA workflow designer. Even people like me, who always likes to choose the "Text" view over "Diagram" view, has had to use it at some point. For example, while adding common transitions.
It is been a while since the last post on the blog. And the last time when the blog was idle for so long, something good was cooking in the background. It turned out to be quite delicious and is known by the name JIRA Development Cookbook!
No price for guessing what comes out this time.
It is my pleasure to announce that JIRA 5.x Development Cookbook is now officially available in the market. The book can be purchased from Amazon or Packt websites.
Recently I came across a simple requirement and saw an exaggerated estimate for that. Well, it isn't all that rare but I was amused how a different line of thought can make all the difference in the world!
Requirement : Make a field mandatory in the workflow screen and make sure the mandatory icon is present on screen.
One fine morning. While zipping coffee on the couch, I made up my design. It is going to be a service that reads configuration data saved using Active Objects. Easy peasy. So I thought!
I wrote my service faster than I planned, looking at my own tutorial, compiled it and everything looked fine.
In the latest versions of JIRA, more and more standard functionalities are pushed into bundled plugins as opposed to the JIRA core product. No better way to showcase the plugin architecture, I must admit!
But that does make the life of high end users, who wants to modify those bundled plugins, a bit difficult.
Let us face it! REST is the order of the day. And Atlassian just underlined that statement with the release of JIRA5.
With JIRA5, a lot of the operations can be done using the REST API and here is the full list of operations supported.
It is simple. Really! To do things that can give a pretty good mileage during plugin configuration, especially for commercial plugins, is simple? Let us see.
In this short recipe, let us look at creating a custom field automatically during a plugin installation and deleting it while un-installation. Same applied for enabling/disabling of the plugin.