User unable to access an issue in Jira with 'ProjectRole should not be null!' and HTTP 500 error page

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

Users will be unable to access an issue and possibly face the 500 error page after performing any of the below actions

  • Importing a project from another Jira instance
  • Importing a workflow from another Jira instance

The following may appear in the atlassian-jira.log

2015-09-24 08:45:16,253 StreamsCompletionService::thread-11 WARN burgeman xxxx xxx xxx.xx.xx.xx /plugins/servlet/streams [atlassian.streams.jira.JiraEntryFactoryImpl] Error creating streams entry
java.lang.IllegalArgumentException: ProjectRole can not be null
	at com.atlassian.jira.security.roles.DefaultProjectRoleManager.getProjectRoleActors(DefaultProjectRoleManager.java:127)
	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.getProjectRoleActors(ProjectRoleSecurityAndNotificationType.java:248)
	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.hasPermission(ProjectRoleSecurityAndNotificationType.java:191)
	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.hasPermission(ProjectRoleSecurityAndNotificationType.java:198)
	at com.atlassian.jira.permission.DefaultWorkflowPermission.allows(DefaultWorkflowPermission.java:48)
	at com.atlassian.jira.security.WorkflowBasedPermissionManager.workflowPermissionCheck(WorkflowBasedPermissionManager.java:217)
2023-06-01 11:02:19,661+0200 http-nio-8544-exec-7 ERROR admin 662x683x1 10fs49k 0:0:0:0:0:0:0:1 /browse/ISSUE-1 [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=3bede74d-24a5-4ec9-a52b-3e248d4b9a0e, interpretedMsg=, cause=com.atlassian.jira.util.dbc.Assertions$NullArgumentException: ProjectRole should not be null!, stacktrace=com.atlassian.jira.util.dbc.Assertions$NullArgumentException: ProjectRole should not be null!
    	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:25) [jira-api-9.4.4.jar:?]
    	at com.atlassian.jira.security.roles.DefaultProjectRoleManager.getProjectRoleActors(DefaultProjectRoleManager.java:100) [classes/:?]
    	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.getProjectRoleActors(ProjectRoleSecurityAndNotificationType.java:185) [classes/:?]
    	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.hasPermission(ProjectRoleSecurityAndNotificationType.java:138) [classes/:?]
    	at com.atlassian.jira.notification.type.ProjectRoleSecurityAndNotificationType.hasPermission(ProjectRoleSecurityAndNotificationType.java:144) [classes/:?]
    	at com.atlassian.jira.permission.DefaultWorkflowPermission.allows(DefaultWorkflowPermission.java:44) [classes/:?]
    	...
    , referer=Unknown, servletErrorMessage=com.atlassian.jira.util.dbc.Assertions$NullArgumentException: ProjectRole should not be null!}

診断

環境

  • JIRA 6.3.12 or above

原因

An invalid workflow property has been configured in the workflow steps. 

Other known issues:

  • JSD-943 - Getting issue details... STATUS

ソリューション

Remove the offending workflow property from the status

  1. Navigate to Project > Project settings > Workflows > Edit the workflow (click on the pencil)
  2. Identify the affected status and click the View Properties link for that status.
  3. Remove the invalid property key.
  4. ワークフローを公開します。


最終更新日 2023 年 6 月 1 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.