[#JRA-2937] Category permission schemes

JIRA

Category permission schemes

Created: 08/Jan/04 12:13 AM Updated: 28/Sep/05 07:07 PM

Component/s:

Permissions Security

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue is related to:

JRA-2018 permission scheme administration improvements

Participants:	Jeff Turner [Atlassian], Michael van Leeuwen, Nick Menere [Atlassian] and Ray Oei [Furore]
Since last comment:	3 years, 2 weeks, 3 days ago
Labels:

Description

« Hide

(From Noel on IRC)

In JIRA Enterprise, it would be nice if one could associate a permission scheme with a Category. Projects in this category would then inherit the category's permission scheme, except where overridden. This would allow the permission scheme for many projects to be changed in one place.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Ray Oei [Furore] added a comment - 14/Jul/04 04:12 AM

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

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 15/Jul/04 01:08 AM

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

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 27/Sep/05 01:04 AM

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

[ Permlink | « Hide ]

Nick Menere [Atlassian] added a comment - 27/Sep/05 02:28 AM

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

Cheers,
Nick

[ Permlink | « Hide ]

Michael van Leeuwen added a comment - 27/Sep/05 03:34 AM

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