How do I restrict different team members access to specific EPICS in JIRA?

[Ernest Lee]

We are planning to setup 1 project to manage multiple small projects across multiple teams. By doing so, is it possible to configure EPIC as small project and restricting access of each EPIC by specific members?  Can someone please advice? Thanks  

[rafal.dubel]

Yo folks!

Check this out: https://confluence.atlassian.com/jira064/configuring-issue-level-security-720412465.html 

[Krisztian Kovacs]

Would it be possible to change security levels based on the epic link via scripting? Is that the tortorous way?

You could use project roles for those security levels.

I may be very very wrong here.

[Nic Brough -Adaptavist-]

Absolutely, both to the security level change via script, and "torturous".

The scripting itself isn't too hard, assuming you've got a scripting add-on, but there's a couple of problems, in that

1.  They won't stop "create"

2. The Epics will be invisible to all the other users, which kind of defeats the purpose of having them

[Nic Brough -Adaptavist-]

You will need to keep the Epics in a separate project if you want to restrict access to them to a set of people.

[Ernest Lee]

So essentially there is no way to restrict access by EPIC in the same JIRA project?  The only way out is by creating different projects?  Is this understanding correct?

[Nic Brough -Adaptavist-]

Correct.

There are some torturous things you can do to make it more difficult (clunky validators in workflows, and javascript hacks to change UI interactions for example), but ultimately if you have access to do something in a project, it applies to all issue types.