How to get rid of the error box "This service project has configuration problems..."

[Jeanne Schock]

This message will not go away. Jira is complaining about missing permissions and the project *may* not work as expected. But it does work exactly as expected, and the permissions are by design. This project has no customers and access is restricted as it is used only to interface with statuspage for public incidents.

In the past when I've had these errors pop up I was able to select Ignore. This one has no such option and will not go away.

Any suggestions for disabling the error or making jira happy without allowing customers to browse, create, or have anything to do with the project?

Errors:

The Service Project Customer - Portal Access security type must be assigned to: Browse Projects Create Issues

The Service Project Customer - Portal Access security type must be assigned to:

[Christopher Yen]

Hi Jeanne,

Hopefully this article can help with troubleshooting what's making Jira unhappy,

https://support.atlassian.com/jira-cloud-administration/docs/resolve-jira-service-management-permission-errors/ 

Typically if we have a project we don't want customers to find we just make sure no groups are added under the people section of the project and as an added precaution

1. from the service desk portal landing page in the top right click your name

2. then click "Page Layout"

3. find the portal associated with the project you'd like to be hidden click the eye icon which will hide it from the home page

[Jeanne Schock]

Hi. I appreciate the response. And this sounds very backwards for Atlassian. Though not surprising.

Why have a permission that can be toggled off, when it is in fact required? Why allow me the option to disable the permission for customers to Browse and Create, and then complain that I'm not allowing them to Browse and Create? And force me to see an error message that will not go away, when the project is working exactly as I want it to because I was allowed to configure it that way?

This is just another example of Atlassian not understanding the many different ways in which its products are being used.