Restrict access to Issues within a specific Projects Component?

Johannes Neuber

I've got the following question: My company wants to migrate to Jira/Greenhopper. All tasks of a project should be tracked. That means, that not only "real" developer/implementation tasks should be tracked, but also all administrative-, project-management-, quality-assurance- tasks. But these tasks/issues should only be visible or editable to/by certain project members (like the project leader, the product owner or whatever). My idea was to create separate Jira Project Components for every sub-process. Now the question: is it possible to configure the Jira Components in a way, that only certain project members have access to it? The advantage would be, that the developers can focus on their technical tasks (because the all the supporting- projectmanagement tasks, are not visible for them).

Thanks in advance.

Johannes Neuber

Nic Brough -Adaptavist-

No. Components are project level items and projects are intended to get people working together. So there's no security on components.

There is a workaround I'd look at, but it needs some code. First, I'd create a security scheme that mirrors your needs - something like "one level per group of people who should see stuff". Secondly, group your users into those groups (or roles, or however you do it). Third, write a listener that sets the security level on any edit, based on the component. You'll need to code for the lowest common denominator though - if someone selects several components, you're going to need to work out which security level gives access to everyone who should see them and use that, it's not a simple "component = security level" mapping.