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

Custom field User Value Permission

Giorgos Savva

Hi world,

I am facing the below issue.

I created a custom field called "Collaborator" with the user-picker (single) type. I added a filter of a group for the user drop-down list. When I try to give the "browse project" permission to the "User Custom field value" of the "collaborator" custom field, then all the portals of the Service Management are visible to all the clients, no matter what other restrictions and permissions I have set.

It's kind of serious. Any ideas?

Accepted answers

Giorgos Savva

Hello all, there is a bug in the Permission Scheme, when assigning to the Custom Field value the Browse Projects permission, projects become visible to any logged-in user on your Jira site including all customers (they were able to see all the SM projects outside their organization.

However the workaround is:

Give the "Browse Projects" permission to a new group
Create A security level where the field value of the custom field has access.

All comments

Jose Luis Gaitan

Hello, @Giorgos Savva . Try to use project roles to distribute the users and give the corresponding permissions to these project roles

Alex Koxaras -Relational-

Geia sou @Giorgos Savva ,

When you mean all the "portals" of the Service Management, you mean "all JSM projects on the portal" are visible? I mean there is only one portal and multiple projects within it.
So if I understood correctly, when you give the Browse project permission for e.g. Project A to the user in the Collaborator field, then that user has visibility of all projects of the portal?

You have to provide a bit more info about your case, since I don't understand what is it that you want to accomplish. If you explain that, we'll be able to assist you further more. (e.g. I don't know if that Collaborator is a customer or a user. And what do you want this collaborator to do within the project.)

Best regards,
Alex

Giorgos Savva

However the workaround is:

Give the "Browse Projects" permission to a new group
Create A security level where the field value of the custom field has access.

Alex Koxaras -Relational-

@Giorgos Savva I don't think that this is a bug and perhaps you get some things mixed up. Can you please tell me the steps you did to reproduce the problem?

Giorgos Savva

@Alex Koxaras -Relational- It is a verified bug according to my discussion with Atlassian support.

So lets see the case again:

You give Jira or Jira Service Management license to a group of people that you do not want to have full access to all the tickets or projects. You add this people in a group ("Collaborators"), and you create a custom field called "collaborator" and you filter only the group "Collaborators" to be available in the drop-down list of the field. Then you give to the "user picker custom field value" the "Browse projects" permission and then the BUG Appears. All Service Management projects become visible to any logged-in user/customer on your Jira site.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-management-cloud

jira-service-management