JIRA 4.0 whats cool and what’s so bad

After looking around for a while for a review of JIRA 4.0 , I didn’t found much of stuff needed seems like people are not talking about it but than I thought lets give JIRA 4.0 much needed review and probably I would be able to help someone and vent out some of my liking and frustrations as one of customware employee and JIRA fan replied to me on twitter

I want to start on happy note so lets start with whats so cool about JIRA 4.0….obvious answer by any big fan will be JIRA gadgets, yes I would say nodding my head in affirmation, gadgets are pretty cool no doubt about them but Atlassian big fat claim that it can work in any social container and any other gadget will work in JIRA’s container is only partly true may be due to some container specific thing or what ever may be the reason for same.

2nd coolest thing is JQL it stands for JIRA Query language, please keep in mind I am calling these things cool and cool is not always the business case, so whats so special about JQL, it allows you to write SQL like queries from with JIRA, which actaully removed alot of or may be all JIRA’s limitation for filtering issues on criteria, now filters in JIRA are much more powerful than ever before thanks to JQL.

I can not control my self and I want to move on to what’s so bad, kindly note my point I am calling bad not uncool to affirm my point that cool is not the business case, first of all the current licensing model simply sucks what costed you $4k earlier now you even get that after paying $8k double appreciation in price in matter of one release, I don’t think any of the Atlassian customers would have ever imagined this catastroph it’s simply ridiculous.

Moving on other perils of JIRA 4.0 is the migration path from 3.13, Atlassian is a very open company they provide alot of documentation helping you in writing plugins and customization you want and than they screw you by breaking the API, I am not a big fan of M$ but one thing I always liked about them is they never break the contract with the developer old API’s always stay. What Atlassian did was just one release and few API’s were gone with the wind without even a single intimation of them being deprecated, I did analysis for efforts required to migrate from JIRA 3.13 to 4.0 for one of my customers and results were not so pleasing from him as they heavily customized JIRA and written around 27 odd plugins and to my surprise none of them worked out of the box in JIRA 4.0 what a crap, I suggested better not to migrate but than Atlassian will stop supporting 3.13 soon than they will be in much bigger soup.

One pending feature for ages better ldap support their strategy on this is pretty clear they want to sell crowd to you and will not add this feature in JIRA, every user comes and reads documentation that it’s planned some where in the road map and buys JIRA in hope he will see it soon but I didn’t got to see it in last 4 yrs , this issue has been recently estimated, I hope it gets completed in this decade, Atlassian has been very prudent in suggesting it’s customers to use crowd for ldap, I liked the business model but I hate it as customer and end user.

I can go on venting my anger on Atlassian but I don’t think they have any concerns about their licensing as alot of people are trapped and they can’t get out of it even they want to, my simple request to Atlassian and all other vendors if you expose API’s to developers than it’s your reponsibility to keep it intact, otherwise better not expose API’s.

PS: Alot of people might ask why I am reacting so late, fact is that this post was in my drafts for quite sometime now I was just not getting impetus to finish it today I had to write something but didn’t had a topic so completed this post