[#JRA-2523] Add per-component permission scheme

JIRA

Add per-component permission scheme

Created: 24/Oct/03 03:33 PM Updated: 26/May/08 05:56 AM

Component/s:

Administration

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-10171~~ Permission schemes to project components

Participants:	A Gouaux, Anton Mazkovoi [Atlassian], Brendan Smith, Bruno Blaise, Daniel Kricke, Dave Loeng [Atlassian], Mark Woon, Matt Vanchura and Sooraj Nambiar
Since last comment:	1 year, 33 weeks, 2 days ago
Support reference count:	9
Labels:

Description

« Hide

Along with per-component owners, it would be nice to have per-component submission schemes as well.

Use case: project has 2 components, A and B. Only some people on the team may be assignable to issues in component A, while everyone is assignable to issues in component B.

Is there any hope for me if I open a feature request for this and and per-component owners on the Professional edition?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dave Loeng [Atlassian] added a comment - 30/Oct/03 12:30 AM

Mark,

Thanks for the feature suggestion. We may look at this for a future version of JIRA.

Cheers,
Dave

[ Permlink | « Hide ]

Matt Vanchura added a comment - 04/Feb/04 04:25 PM

We too have a need for this:

We have a main project called Production Support.
Anything that is not a new project under development gets lumped into this main project and is setup as a Component under this project.

If we could apply Permission schemes to the Component level, we could give access to other business units for just the applications that fall under their particular realm. This would allow us to restrict the issues they could see to only the applications that the business unit is related to.

[ Permlink | « Hide ]

Brendan Smith added a comment - 11/Nov/04 01:27 PM

This would also be a very useful feature for us, as we will need to create seperate projects to maintain security, which complicates our Jira schema.

[ Permlink | « Hide ]

A Gouaux added a comment - 20/Jul/05 08:43 AM

I believe in the Enterprise Edition it is possible to group projects together into something like a project container, however I cannot seem to find the documentation for this despite searching around for 30 minutes or so this morning.

Anyway... it seems to me that ~~JRA-3924~~ JRA-3838 JRA-5276 this issue and possibly others could all be satisfied by "simply" allowing for true nesting of projects. That is, allow for one or more projects to be fully nested beneath an encompassing project. This encompassing project would be much more than just a container. All those with access to the encompassing project would have similar access to the nested projects.

Yeah I know. Easier said than done.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 21/Jul/05 09:58 PM

Hi,

If issues in a certain component need to be controlled by separate permission please consider turning a component into a separate project.

We are hoping to imlement a proper project category hierarchy and allow schemes to be associated with any point in the hierarchy in the future.

As you have mentioned, it is not straight forward to implement, so it wll take us some time

Anton

[ Permlink | « Hide ]

Sooraj Nambiar added a comment - 28/Mar/06 06:33 AM

We do have same request where we have multiple clients and need to monitor their issues. Only way we can do now is, create separate project for each client. I created components, but couldn't implement it since all clients will see other components which is not necessary for them. So component level access would be a great solution to overcome this.

Sooraj.

[ Permlink | « Hide ]

Bruno Blaise added a comment - 21/Sep/06 10:54 AM

I have as well the same request, please investigate on this request

[ Permlink | « Hide ]

Daniel Kricke added a comment - 09/Jan/07 08:47 AM

Hi,

we also have the same problem, we need a project hierarchy so that we are able to assign specfic permission scheme to "subprojects" (currently components).

thx