Comments on: JIRA 4.0 whats cool and what’s so bad http://www.singhvishwajeet.com/2010/04/27/jira-4-0-whats-cool-and-whats-so-bad/ My experiences Tue, 13 Dec 2011 19:39:08 +0000 hourly 1 http://wordpress.org/?v=3.1 By: Vishwajeet Singh http://www.singhvishwajeet.com/2010/04/27/jira-4-0-whats-cool-and-whats-so-bad/comment-page-1/#comment-4995 Vishwajeet Singh Thu, 29 Apr 2010 16:49:23 +0000 http://www.singhvishwajeet.com/?p=285#comment-4995 Thanks for your reply much appreciated will get in touch once I hear from customer on his upgrade plans, thanks once again. Thanks for your reply much appreciated will get in touch once I hear from customer on his upgrade plans, thanks once again.

]]> By: Edwin http://www.singhvishwajeet.com/2010/04/27/jira-4-0-whats-cool-and-whats-so-bad/comment-page-1/#comment-4991 Edwin Tue, 27 Apr 2010 19:01:41 +0000 http://www.singhvishwajeet.com/?p=285#comment-4991 Hi Vishwajeet, Disclaimer: I'm from Atlassian working on JIRA. Firstly, thanks for taking the time to review and write about JIRA 4. It's great that you liked the new dashboard and JQL. With regards to some of the points you mention: >> 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 The pricing changes were not something that we undertook lightly, and certainly not something that we did to "create more profit". In fact, the pricing changes in JIRA 4.0 came about because we wanted to better reflect the needs of our customers. We understand that for some customers, this may have negatively impacted them, but what we found was that most of our customers ended up paying less, not more, under the new licensing scheme and had access to all the functionality of JIRA. For example, the cost of JIRA for small and medium teams were drastically reduced. In addition, we also provided generous upgrade options for existing customers under our grand fathering schemes (http://www.atlassian.com/software/jira/licensing-changes-faq.jsp#10). >> 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. Unfortunately, this was one of the trade offs and challenges that we faced during development. JIRA 4.0 was a significant release which required many changes to the internals of the system. We have also ran an extensive beta program with the hope that plugin developers had the opportunity to upgrade their plugins to use the latest API. In general, we aim to minimize the impact to plugins during our development, but that may not always be possible. As the codebase of JIRA evolves, we'll also be looking at ways to produce a clearer set of APIs that plugin developers can rely on. >> 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 Improving the LDAP support in JIRA is something that we are actively working on in JIRA, so we are committed to delivering this feature. Unfortunately, this is a project of considerable engineering size and risk to get right, so we're taking some time to get to the end of it. I'd be glad to discuss more details about the challenges you faced directly offline if you would like. Just drop me an email. Regards, Edwin Atlassian Product Management Hi Vishwajeet,

Disclaimer: I’m from Atlassian working on JIRA.

Firstly, thanks for taking the time to review and write about JIRA 4. It’s great that you liked the new dashboard and JQL.

With regards to some of the points you mention:

>> 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

The pricing changes were not something that we undertook lightly, and certainly not something that we did to “create more profit”. In fact, the pricing changes in JIRA 4.0 came about because we wanted to better reflect the needs of our customers. We understand that for some customers, this may have negatively impacted them, but what we found was that most of our customers ended up paying less, not more, under the new licensing scheme and had access to all the functionality of JIRA. For example, the cost of JIRA for small and medium teams were drastically reduced.

In addition, we also provided generous upgrade options for existing customers under our grand fathering schemes (http://www.atlassian.com/software/jira/licensing-changes-faq.jsp#10).

>> 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.

Unfortunately, this was one of the trade offs and challenges that we faced during development. JIRA 4.0 was a significant release which required many changes to the internals of the system. We have also ran an extensive beta program with the hope that plugin developers had the opportunity to upgrade their plugins to use the latest API.

In general, we aim to minimize the impact to plugins during our development, but that may not always be possible. As the codebase of JIRA evolves, we’ll also be looking at ways to produce a clearer set of APIs that plugin developers can rely on.

>> 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

Improving the LDAP support in JIRA is something that we are actively working on in JIRA, so we are committed to delivering this feature. Unfortunately, this is a project of considerable engineering size and risk to get right, so we’re taking some time to get to the end of it.

I’d be glad to discuss more details about the challenges you faced directly offline if you would like. Just drop me an email.

Regards,
Edwin
Atlassian Product Management

]]>