No permission scheme is associated with project

[Christopher Gronde]

We recently deleted a project that was no longer needed.  Now our logs are being exploited with a constant entry of the following:

2019-03-12 13:30:37,953 http-nio-8080-exec-26 WARN anonymous 810x4424x1 - xx.xx.xx.xx / [c.a.jira.permission.DefaultPermissionSchemeManager] No permission scheme is associated with project 'PROJECT_NAME'

How do we stop this entry from occurring and how do we properly delete projects in Jira Server in order for this to no longer happen.

(Jira Server 7.13.0)

We found the following groovy script that claimed to fix this issue but it only returns an error.

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.permission.PermissionSchemeManager;
import com.atlassian.jira.scheme.SchemeManager;
import com.atlassian.jira.scheme.Scheme;

def prList = ComponentAccessor.getProjectManager().getProjectByCurrentKey("PROJECT_KEY")
PermissionSchemeManager permissionSchemeManager = ComponentAccessor.getPermissionSchemeManager();
Scheme permissionScheme = permissionSchemeManager.getSchemeObject("SCHEME_KEY");
permissionSchemeManager.addSchemeToProject(prList, permissionScheme);

It only returns: The scheme passed can not be null.

[John Shoemaker]

We have same issue. The operations that we believe caused the issue are as follows: moved some JIRA issues from original project to a new project, deleted the original project. We have confirmed that the project did delete. Could it be that the "moved" issues have caused this error?

[Nic Brough -Adaptavist-]

If you've done all these moves within the UI (or over REST). then no, it should not be anything to do with issues being moved around.

This is usually broken data in the database, which mostly only happens when people write to the database or write scripts that do bad things.

[Nic Brough -Adaptavist-]

The script needs project_key and scheme_key replaced with the IDs of the project that is broken and the scheme you want to swap it to.

[parthiban_selvaraj]

Hi @Nic Brough -Adaptavist- @JamieA ,

We are facing the below error on log

2019-08-01 12:05:11,732 http-nio-8081-exec-131 WARN XXXX  /rest/api/2/issue/XXXX-3344 [c.a.jira.permission.DefaultPermissionSchemeManager] No permission scheme is associated with project 'dummy_project'
2019-08-01 12:05:11,733 http-nio-8080-exec-652 WARN XXXX rest/webResources/1.0/resources [c.a.jira.permission.DefaultPermissionSchemeManager] No permission scheme is associated with project 'dummy_project'

We dont have any project with the following Key "Dummy_project". Kindly help us to solve the above error.

Thanks,

Parthiban

[Nic Brough -Adaptavist-]

You need to replace "Dummy_project" with a project that does exist in your system then!

[parthiban_selvaraj]

Hi @Nic ,

Thats the problem, we dont have any Project in Jira with the name "Dummy_project".

But we facing "No permission scheme is associated with project 'Dummy_project' ".

If I try to update any existing Project name as "Dummy_project" am getting the below error msg [A project with that name already exists]. 

Kindly help us to resolve the issue, our Log is flooded with above error msg.

[Nic Brough -Adaptavist-]

It sounds to me like you have broken your data, probably by executing SQL in the database or possibly a bad script.  You'll need to undo that damage.

[parthiban_selvaraj]

Hi @Nic Brough -Adaptavist- ,

Do you have any idea to resolve the issue, kinldy help us to overcome this issue. 

Thanks,

Parthiban

[Nic Brough -Adaptavist-]

We need to know what you did to the project that is broken, in order to help you undo it or work around it.

[Kamil Kolonko]

@parthiban_selvaraj could you please verify if the project is present via System settings -> Projects menu (/secure/project/BrowseProjects.jspa?s=view_projects). This action requires sysadmin permissions.

Possibly you're not seeing the project via /secure/BrowseProjects.jspa list because as the error message says, no permission scheme is associated with it which means the application cannot evaluate if you have permissions to see it. /secure/project/BrowseProjects.jspa endpoint skips these permission checks.

In order to resolve your issue you'd have to try removing the project again.

[parthiban_selvaraj]

Hi @Kamil Kolonko , 

I resolved the issue and what you suggested is correct. I missed out to check it in System settings -> Projects menu . Instead of that I tried everything in DB and Scripts.

Thanks for your info.

CC @Nic Brough -Adaptavist- 

[Brant Schroeder]

I have run into this before where the project did not actually delete because there were too many comments on an issue so the project delete ended up failing.   Go to projects in the administration section and see if the project still exists or not.  If it does then you can reapply a permission scheme following these directions: https://confluence.atlassian.com/jirakb/unable-to-access-a-project-permission-scheme-configuration-due-to-nullpointerexception-297670208.html  You will then need to find out why the project is not deleting and fix it.