Project Level Security in JIRA

[Rolondo Talbott]

We are implementing JIRA in our IT Department. The desire is that every user has the ability to create projects and issues, create workflow, etc. 

On Project led by a Project Manager or our PMO, the desire is that users ability be limited to the role they are performing (e.g. developers can only open issues). Is there a way to have JIRA instance security and Project-based security - which may differ depending on the Project role?

[Alexey Matveev · Accepted solution]

Hello,

You need to provide cases, how you want to restrict users.

If to answer the cases you provided:

1. If you want to each user to create projects, issues, create workflows then you would need either to make all users Jira administrators or let the users to create next-gen projects

2. If you want to limit developers only to open issues, then you need a classic project and grant the Developer role only the Browse Projects permission and Create Issues permission.

[Rolondo Talbott]

I believe the use case is exactly how you described. On Projects, a developer should have the ability to create issues within an Epic. From what you wrote, it sounds like we would need to create a CLASSIC Project.

However, should a developer need to create their own Projects, Boards, Issues, etc, they would use the Next Generation Project?

Assuming I have that correct, is that one of the key differences between Classic and Next Gen - security around Project roles? And, if so, does selecting Classic over Next Gen take into account the role they have within JIRA itself (not just on a project)?