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; } } }

User Permissions on Team Managed Project

Alisa Collins

We have clients invited to our project board. I would like to restrict visibility for them ONLY see issues they created, are assigned, or are tagged in.

I have GROUP setup for them - I also have a specific ROLE for them. Again, this is a TEAM managed project.

Do I have any options?
Permissions at the role level are not clear - but testing we haven't found the right combo (if there is one).

If not this, on at TEAM managed project, is there a way to set an ISSUE type permission that would only allow them to create and SEE issues of that type?

Many thanks.

Accepted answers

All comments

Mikael Sandberg

Hi @Alisa Collins,

Welcome to Atlassian Community!

No, team-managed project cannot set the view level on individual issues, you can only restrict who can view different issue types. In order to restrict issues to just the ones that they created, are assigned to or watching you have to use a company-managed project and security levels.

Trudy P Claspill

Actually @Mikael Sandberg that is not true.

You can set restrictions on individual issues as well in Team Managed project. Through the UI you do so by clicking on the padlock icon.

Screenshot 2024-08-14 at 3.09.41 PM.png

@Alisa Collins You can set visibility of issues based on their Type, giving specified project Roles visibility to all issues of specified issue type(s). That does not give you the granularity to restrict visibility to "issues they created, are assigned, or are tagged in"

It should also be noted that there was a Sept. 2023 post where I and others were trying to explore setting issue restrictions in a Team Managed project via Automation Rules, and we were unsuccessful.

https://community.atlassian.com/t5/Jira-questions/team-managed-project-set-security-level-when-transit-to-certain/qaq-p/2468632

Also, since restrictions are based on Project Roles you would have to basically have a unique Role for each user. If User A and B shared role XYZ, and only user A was the Creator, current Assignee, or Mentioned in an issue, if you restricted the issue to Role XYZ then that would enable User B to see it also. That doesn't match your requirement.

You would have to have a unique Role per user for the users for whom you needed to restrict issue visibility, plus a Role for the users who need to be able to see all issues. Each issue would have to be checked to see which of the client users was the Creator, current Assignee, or mentioned in the issue so that their Role could be added to the Restrictions, along with the Internal Team's Roles being added. And each time the Assignee changed or a new Mention happened, the checks would have to be done again.

And you would have to set restrictions on every issue. If an issue did not have any restrictions set, then it would be visible to all the clients.

In conclusion, I don't believe there is a solution to your requirement as long as you are using a Team Managed project.

Alisa Collins

Thank you both for this information. At least I know that I'm not missing something.

I'm not sure the restriction of issue type will work--but may be better than nothing.

Alisa Collins

@Trudy P Claspill

I've attempted to set a role with limit to only see BUG tickets.
I asked this user to log out and back in - and provided him with a link to the Board.
He is still seeing other types of tickets.
Am I doing something wrong?
Screenshot 2024-08-16 at 8.07.18 AM.png Screenshot 2024-08-16 at 8.06.56 AM.png

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

permission

team-managed-projects