Erik,

We have done nothing but consider alternative to Jira. Frankly, it shocks me what Atlassian gets away with. I'm assuming the business environment and legal system in Australia is out to lunch.

That said - can not find alternative as of yet. AND THIS IS WHY ATLASSIAN GETS AWAY WITH MURDER. Developing a competing product is not a big deal and would take far less energy then what Jira users have pissed away with this hack product.

Atlassian should focus on customer-satisfaction. We are using JIRA for support, less than 10 people supporting more than 100 customers (so we need to buy a 500license, so far so bad).
Only internal user should have access to AGILE. We did not accept to pay a AGILE license if around 490 licenses or 98% will be unused until end of earth.

I personally am less concerned on the cost component, as compared the issue of content control. In particular, my management dislikes having to have entire projects created to have a private Kanban board for organizing their work... Particularly because that means they can't share issues with non-management.

This has actually gotten to the point that they are considering a competing product (as opposed to expanding JIRA) solely because the alternative is not being able to use JIRA as desired.

Absurdo!!! Onde fica a segurança?
Favor reconsiderar a decisão, pois precisamos restringir a visibilidade do agile de acordo com os grupos ou projetos dos usuários.

I totally agree! I really don't understand why Jira Agile is not restrictable for a group of users - We currently habe 8 Users using Jira Agile and other 42 that are not, but those 42 Users can access the boards bur don't understand what they mean,... this is really stupid! On the other side, why do I have to pay for 50 Users when only 8 use it!

Absurdo!!! Onde fica a segurança?
Favor reconsiderar a decisão, pois precisamos restringir a visibilidade do agile de acordo com os grupos ou projetos dos usuários.

We're using JIRA as both our internal engineering Scrum tool and as our customer facing support ticket tool. Our external customers should not be seeing an Agile menu since it has no relevancy to them, and we shouldn't have to run two completely separate JIRA instances in order to accomplish this. With the advent of "JIRA Service Desk" in which Atlassian seems to be promoting the use of JIRA as a customer facing support ticket tool, it makes the omission of this feature even more glaring. Please reconsider opening this issue?

It's not just the separate licensing model (would be nice, yes) ... but for us it's important to restrict certain GreenHopper actions (like Backlog Grooming, Creating Boards, Creating Sprints) only to Product Owners. Developers and especially Freelancers/Contractors should definitively not be able to mangle with these things!

This is really a big mess!!!!

In our Company we use jira for nearly everything. We use a 50 User License. Greenhopper would be great for our developer and technical team that would be only between 5 and 10 Users.

Why ca't I licence Greenhopper for 25 and Jira for 50??

Seconded. Atlassian - you are flushing cash down the toilet here by missing out all the folks that would buy Greenhopper 25 user licenses for their SW dev teams but have unlimited JIRA users, versus not buying Greenhopper at all. Poor form indeed.

The current status no longer applies. Please reconsider this issue immediately. We use JIRA for far more than Agile development, out of 100 users only 20 are developers and only 20 need Greenhopper. We will not license Greenhopper for all 100 users, it is not an option.