Wow, it's been a while since the last post. Crazy schedule but this one is too cool to ignore!
Ever wondered how the nice little JIRA notification messages are created? The ones you get when an issue is created in JIRA?
Doing this is so easy that you will want to try it out in every new plugin that you write!
With 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.
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.
Everyone knows how the usage of proper decorators can get you the desired look and feel.
Have you been paying attention to the JIRA Decorators as well? If not, read on..
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.
It is actually a follow-up post. A follow-up to the question Mizan asked in my last post. Before you proceed, here is warning: Strictly for AJS novices, like me!
In this post, we are looking to prepopulate jira fields based on the current user's group. And we are gonna use AJS for the same!
Agile advocate in the room is screaming! How can you have 2 fix versions for a single ticket? How? How? How?
Several scenes (and days) later, Scene N:
Q: We need to restrict the fixVersion(s) field to have only one version. And we need it before the next meeting. Can you?
A: Yup, you are not the first one to ask. Let's do it!
Often we come across scenarios where we need to add a new link in JIRA under various places in the user interface. The first thing that comes to mind is "Oh I need to modify the jsps and that means my upgrades are going to be a nightmare"! But hang on, JIRA is far better than you think!
Adding a link is JIRA can be achieved pretty easily by writing a web-section and/or web-item plugin module. And that doesn't involve writing any programming languages, including JAVA.