Hi david.arndt,

We're still working on improving permissions overall in JIRA and internally have initiatives to make significant improvements. I won't go into detail right now to avoid any mismanagement of expectations but it is worth saying that permissions is not something we will soon neglect in JIRA.

Please email me if you have any more questions

Kind Regards,
Kerrod

Hi Kerrod,

that's disappointing.
You are still working on improving permissions in general, though?
Permissions are one of the central features that are lacking more precise settings.
It's not an option to buy plugins for every missing feature.

Best Regards
David

Thanks for taking the time to raise this issue.

Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

Kind Regards,
Kerrod Williams
JIRA Product Management
kerrod.williams at atlassian dot com

This is a needed function for our use at SAS.

Hi Nick,

That's why I added a link (which is now duplicated). When having a lot of
projects, a category could indeed be preferrable, but it should then apply to
all schemes, since only selecting a Category or a permission scheme makes no
difference. Or inheritance should be applied to projects (currently not
supported and not raised as an issue).

So, in the current description, this issue is a non-issue IMHO.

Regards,
Michael.

–
_____________________________________________________________________
Nu 12 maanden gratis Live Eredivisievoetbal bij 20 Mb ADSL voor maar
EUR 39,95 per maand. Bestel op www.versatel.nl/voetbal

Michael,
It is a very good idea though this is already an open feature request at JRA-2018.

Cheers,
Nick

To solve the problem of changing a permission scheme for many projects in one place, why is it not possible to use template groups to assign permissions?

Clarification:
Allow to specify groups with for example the following names:
${key}-users, ${key}-developers, ${key}-managers, ${key}-bizusers, ${key}-qa
In which the ${key} is automatically replaced with the project-key. In project 'JIRA' it is group JRA-users having the permissions, while in project 'Confluence' the group CONF-users is assigned those permissions

This technique is already applied to the plugin at http://confluence.atlassian.com/pages/viewpage.action?pageId=118605

Incidentally, one way to lessen the pain of creating new almost-the-same project configurations is to have a prewritten Jelly script. There is an example at:

http://www.atlassian.com/software/jira/docs/latest/jelly.html#examples

Yes that would simplify configuration a great deal. Mainly because I will need te configure a lot of projects ('helper'applications) in the project category (teh 'main project').