nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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:

Screenshot 2021-08-26 at 22.12.26.png

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".

Accepted answers

Ivan Lima

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.

All comments

Ivan Lima

Jonas Tidström

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

Screenshot 2021-08-27 at 21.24.51.png

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.

Screen Shot 2021-08-27 at 3.47.24 PM.png

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.

Screenshot 2021-08-28 at 17.27.18.png

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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud