One of the service desk projects has disappeared and is not listed in the Add Project in customer po

Hi @Walter Buggenhout 

Thank you for the response. The project exists it works normal when we disable the Refined For Jira and is appeared in the customer portal. However once the refined is enabled this particular Service Desk project disappeared and is not listed to add this project from Refined site builder.

Looks like an issue with Refined. I have uninstalled and reinstalled the Refined still the issue exists. Well I have opened support case with Refined for their response and support.

Thank you for your time.

We are having the same thing.  It's like all of our Service Management projects are just suddenly unavailable and missing.

I can access them via direct link or from the project via the Raise a Request button, but the search navigation widget is missing and if I go to edit them, nothing appears but a blank screen.  If I go to the Site Builder under Refined Administration, several projects are just suddenly missing.

Hello @Sshah and all,

I found a temporary workaround to solve this problem.  I presume you have the Extension for Service Desk plugin made by Deviniti in addition to the Refined plugin.  If so, try the steps below.

1. Load your Refined Admin console and go to the Site Builder tab where you see (or more accurately, currently DON'T see your projects).  Keep this tab open.
2. In a separate tab, in Jira, go to a project that isn't appearing on your Site Builder list but should be / used to be.  Go to that project's Project Settings.
3. After loading the Project Settings, go to Extension --> Visibility --> Customer Portal tab.  Temporarily add a group you are a member of to the Selected Groups field.
4. Refresh the Site Builder tab you loaded in step 1.  Does the project now appear in the list?  If so - This confirms this is a permissions conflict/quirk going on between the Refined and Extension for Service Desk plugins.

I'm temporarily resolving mine by adding everyone in our organization to a group and then giving that group access to view the portal.

Ideally, we would be able to leave that field empty and not do this, but it can at least temporarily solve the issue until the plugin developers can patch this.