Default project roles when applying issue restrictions

María José Villanueva

I am studying for the ACP-620 exam and I have the following doubt.
When a team-managed project is open, I can see that all jira users can browse the project and edit all issues. However, when I restrict an issue by the role Member, I experience a different behavior. The courses and the documentation say that when a project is open, the role "member" is given by default. But I have checked the permission helper and the error I got is that the user does not have the corresponding role.

Is then required to add the user to the access of the project with the correponding role or I am missing something?
Best regards and thank you.

Emma Wolstencroft

Hi @María José Villanueva ! Thanks for posting this. I appreciate it's confusing. 

All users are given the membership of the Member permission role for that project. This refers to the permissions for the whole project.  The Member role manages their permissions in the project generally, like their ability to edit issues and so on. However, they are not granted the project role of Members. They are not added to the Members project role, which is used for page restrictions etc. This would need to be done explicitly. 

In reality, you would never restrict a page to the role of members when you're in an open project; it would make no sense. I appreciate that it's possible, but it would not be advisable. You would instead create a custom role and restrict issues using that role. 

The important thing to know is that since it would not be advisable to do this, we do not test on this area. You will not find questions that refer to restricting access to individual issues using the members role in TMP. 

I hope this makes sense.