Users with correct permissions can't access configure board

Still need help?

The Atlassian Community is here for you.

Ask the community

 

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

Problem

When user with right permission tries to access any of the board, there's be following error thrown by JIRA:

 

Error

parameter should not be null!

 

When this specific error is shown in JIRA, there''ll be specific error logged in atlassian-jira.log

2016-05-11 22:35:33,951 http-nio-8421-exec-19 ERROR charlie 1355x4633x1 v9ts9u 10.60.3.121 /rest/greenhopper/1.0/rapidviews/viewsData [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: parameter should not be null!
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: parameter should not be null!
	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:25)
	at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:92)
	at com.atlassian.jira.security.type.SingleUser.hasPermission(SingleUser.java:82)
	at com.atlassian.jira.permission.DefaultPermissionSchemeManager$5.hasPermission(DefaultPermissionSchemeManager.java:453)
	at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:613)
	at com.atlassian.jira.permission.DefaultPermissionSchemeManager.hasSchemePermission(DefaultPermissionSchemeManager.java:450)
	at com.atlassian.jira.security.DefaultPermissionManager.doProjectPermissionCheck(DefaultPermissionManager.java:185)
	at com.atlassian.jira.security.DefaultPermissionManager.hasPermission(DefaultPermissionManager.java:107)
	at com.atlassian.jira.security.WorkflowBasedPermissionManager.hasPermission(WorkflowBasedPermissionManager.java:110)
	at com.atlassian.jira.security.DefaultPermissionManager.lambda$getProjectObjectsWithPermission$1(DefaultPermissionManager.java:292)

Diagnosis

Diagnostic Steps

  • Since the error message seems to be specific to the null values in Permission Schemes, we can check the Permission Scheme used by the project to see whether there's any null values associated with any of the permission.
  • Run the following query to check whether there's any null value associated to the specific permission:

    SELECT * FROM schemepermissions WHERE perm_parameter is null AND perm_type = "user"; 
  • The query above should show similar result as below:

    +-------+--------+------------+-----------+----------------+---------------------------+
    | ID    | SCHEME | PERMISSION | perm_type | perm_parameter | PERMISSION_KEY            |
    +-------+--------+------------+-----------+----------------+---------------------------+
    | 13202 |  11130 |       NULL | user      | NULL           | ASSIGN_ISSUES             |
    | 13654 |  11134 |       NULL | user      | NULL           | ADMINISTER_PROJECTS       |
    | 13674 |  11134 |       NULL | user      | NULL           | MANAGE_SPRINTS_PERMISSION |
    +-------+--------+------------+-----------+----------------+---------------------------+

 

Cause

The error occurs because there's null value associated to the specific permission.

Resolution

To resolve the issue, we can delete the null values so it does not associate with the specific permission. To find out which permission contain the null value, please run the query below:

SELECT * FROM schemepermissions WHERE perm_parameter is null AND perm_type = "user"; 

From the query result, you can use the SQL query below to delete each of the null value:

(info) Please  backup your JIRA before deleting the data from your database.

DELETE FROM schemepermissions WHERE ID = XXXXX AND SCHEME = XXXXX;

Restart your JIRA 

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.