Functional warnings when changing permissions.

[Ian Guyette]

Hi, I'm working on a service desk project and I frequently receive the errors noted in the attached image: 

The issue is that I would prefer that the project is hidden from the portal to everyone except the project admins/technicians. This should not be a customer-facing project/portal for requests at this time. Further, I do not see why disabling the requestors from changing their reporter status would break anything... it is in our interest to prevent them from accidentally or intentionally requesting something on behalf of another person. 

Anyone have any insights on this? 

[Anthony Morais · Accepted solution]

Hi @Ian Guyette 

For each of your JSM projects, you just need to change the "Customer Permissions" in the project settings to the "Customers added to project" option. Thus, if a client is not added to the specific project(s), he/she will not be able to view the projects listed in the portal.

If your plan is free, do the following:

You need to remove the "Browse Project" permission -  Customize Jira Service Management permissions:

Permissions for customers must be granted to the Service Desk Customer - Portal Access security type, not the Service Desk Customers role. The Portal Access security type allows customers to access the customer portal, but not Jira. The security type reads the role to determine who the customers are.

• Create Issues (customers can create requests and view submitted requests through the customer portal)

• Browse projects (customers can access the project from the customer portal)

• Add comments (customers can comment on their requests).

• Create attachments (customers can add attachments to their requests)

• Assign Issue (This permission is required for the Assigned field to work. The Assigned field is an optional hidden field and automatically funnels Issues to certain team members.)

I hope it solves.

Thank you and if it solves it please mark it as accepted answer!

Anthony

[Ian Guyette]

Thanks Anthony, will go this route. 

[Brant Schroeder]

@Ian Guyette This is caused when the Service Project Customer - Portal Access role is not assigned to the two permissions referenced.  

You will need to update the project permissions with this role.