Restrict issues access in next-gen team-managed project not working for me

[Jonas Tidström]

I want to restrict access to a specific issue type "Meta" for users that are part of a specific group "VCS". In setting>issue types it should be possible to do this:

Now, a user Adam in group VCS, should not be able to see newly created issues of type "Meta" since VCS has been assigned role "Member".

However, Adam can see newly created "Meta" issues, even though that user shouldn't be able to do that.

Why? Am I doing something wrong...? Any suggestions are deeply appreciated!

---

The user Adam is in group VCS and in no other groups and has a role "basic" on the user detail's page.

The user Adam has not been invited to the project individually. Adams access to the project is set by the group VCS.

The group VCS has been assigned role "Member".

/J

[Ivan Lima · Accepted solution]

Hi @Jonas Tidström. It sounds about right to me what you described. What did you get when you run to the permission helper? Go to the permission helper, select the user (Adam), the issue you believe Adam shouldn't see, and Browse Projects under permission.

[Jonas Tidström]

The following is the output when running the permission helper according to the instruction of @Ivan Lima 

[Ivan Lima]

I have the same scenario, and you should see something like my screenshot. Assuming your Meta-42 was created after adding the restriction to the Administrator group, you should see the issue security. Have you tried adding the user to the role Member rather than via group? Just throwing some ideas out to help you isolate/troubleshoot it.

[Jonas Tidström]

Thanks @Ivan Lima for helping me out! I tried your suggestion but with no luck. But your screenshot give me some clues. You user Joao does not have "browse projects permission", while Adam does.

However, no matter how I go about it, Adam either has no access to the project at all, or access to "browse projects".

My problem has led me to the following note from Atlassian. 

https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/

This may or may not be relevant to my case. Right now I am mostly amused by considering how much time one can spend on this — and still have not resolved it :) 

A question just to be certain: can Joao access the "MNT project"and see other "normal" issues? 

[Ivan Lima]

Ok, let's not giving up just yet. I don't believe it's relevant for this use case, but it's a good point. In my example, Joao can access the project and see issues other than Task. I'll share my setup, and you can compare it on your end to spot if you see any difference, which can give you a clue as to where the configuration issue might be. 

1) Let's look at Joao's access. Member of VCS and jira-software-users. Site access and access to Jira Software.

2) Project access (team-managed project). VCS assigned to the Member role. I'm assigned to the Administrator role.

3) In this example, my issue type Task has been restricted to the Administrator role.

4) Lastly, newly created issues of type Task are now restricted to Administrators, and Joao can't see them.

I'm now curious to know what the differences are. If you can't spot any, meaning you've got the same configuration and are still facing challenges, it can be a bug.

[Jonas Tidström]

Appreciate you help! I used another created issue type "Meta" in my first round... That was the only difference in the setup. So, I tried to restrict the default issue "Task" instead so that my configuration is completely analogue to yours. Still no luck. I have filed this as a bug. Many thanks!