-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
We are using JIRA now in a small team (4 or 5 people) with the possibility of expanding it company-wide (which would be 200+).
With the new "starter kit" pricing I decided to evaluate Greenhopper as well. Not sure if we'll use it, but in any case, should we get the 100+ license for JIRA, we are unlikely to want to pay for everyone to use Greenhopper as well, more likely the 25-user option. Most of our users of issue tracking software are very casual, simple users and don't need bells and whistles.
Right now it looks like whatever the license for JIRA (10, 25, 50, 100, 100+), if you buy Greenhopper you have to have the same license. That seems silly, please decouple the licensing so that if most users don't need the extra features, we don't have to pay for them to sit unused.
- is cloned from
-
- Closed
- is incorporated by
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-1975] Decouple greenhopper licensing from JIRA licensing
Brett Adam
added a comment - This is a blocker to any sales activity for us. Brett Adam
added a comment - We're a long time JIRA customer, now considering GreenHopper.
However, the pricing is prohibitive for us given the way you've linked JIRA user count to GreenHopper licensing.
Here's our situation:
We have a single JIRA instance at http://issues.rpath.com
We serve three audiences with this instance:
1/ The Open Source community around our core technologies (Conary, rMake, rPath Linux, rBuilder Online)
2/ Our commercial customers for rBuilder (on premise product).
3/ Internal Engineering and Support team members that service both 1/ and 2/
Because we have this public-facing, open issue tracking model that also integrates our support and engineering processes, we have an Enterprise (Unlimited) user JIRA license.
However, the engineering and support teams are the only folks that need the GreenHopper features. Indeed, I do not want to expose those features to audiences 1/ and 2/
The user count of Eng and Sup is < 25 people.
Hence, I'd love to consider GreenHopper for the 25 user license immediately, upgrading to perhaps the 50 user license next year.
Can this be done? Or do I need to forget about GreenHopper?
Brett Adam
added a comment - We're a long time JIRA customer, now considering GreenHopper.
However, the pricing is prohibitive for us given the way you've linked JIRA user count to GreenHopper licensing.
Here's our situation:
We have a single JIRA instance at http://issues.rpath.com
We serve three audiences with this instance:
1/ The Open Source community around our core technologies (Conary, rMake, rPath Linux, rBuilder Online)
2/ Our commercial customers for rBuilder (on premise product).
3/ Internal Engineering and Support team members that service both 1/ and 2/
Because we have this public-facing, open issue tracking model that also integrates our support and engineering processes, we have an Enterprise (Unlimited) user JIRA license.
However, the engineering and support teams are the only folks that need the GreenHopper features. Indeed, I do not want to expose those features to audiences 1/ and 2/
The user count of Eng and Sup is < 25 people.
Hence, I'd love to consider GreenHopper for the 25 user license immediately, upgrading to perhaps the 50 user license next year.
Can this be done? Or do I need to forget about GreenHopper? 
Please reactivate this issue or incorporate the goal into the parent issue
GHS-1374.Thanks.
Andreas