Details
-
Bug
-
Resolution: Fixed
-
Highest
-
Severity 1 - Critical
-
Description
Description
By somehow, when we only have Next-Gen projects created, the issue type Story from the classic projects are being used for the Next-Gen project and makes impossible to create new classic projects
Steps to reproduce
We were not able to reproduce those issues
Errors
The following error is displayed: "For some reason the magic didn't happen. Click Create to try again"
Although the project isn't created, Jira still creates all of its schemes (issue type, workflow etc).
Splunk
msg: Illegal Entity Scope for Entity class (ISSUE_TYPE). Expected entity scope 'GLOBAL' but has scope 'PROJECT' stack: com.atlassian.jira.scope.IllegalScopedEntityArgumentException: Illegal Entity Scope for Entity class (ISSUE_TYPE). Expected entity scope 'GLOBAL' but has scope 'PROJECT' at com.atlassian.jira.scope.EntityScopeUtil.assertGlobalScope(EntityScopeUtil.java:157) at com.atlassian.jira.scope.EntityScopeUtil.assertGlobalScope(EntityScopeUtil.java:144) at com.atlassian.jira.issue.fields.config.manager.IssueTypeSchemeManagerImpl.lambda$assertMutatorDoesNotAffectNonGlobalEntities$21(IssueTypeSchemeManagerImpl.java:829) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) msg: An error occurred while notifying that a project was created stack: java.lang.RuntimeException: An error occurred while notifying that a project was created at com.atlassian.jira.bc.project.DefaultProjectService.notifyHandlersOfProjectCreated(DefaultProjectService.java:420) at com.atlassian.jira.bc.project.DefaultProjectService.createProjectInternal(DefaultProjectService.java:357) at com.atlassian.jira.bc.project.DefaultProjectService.createProject(DefaultProjectService.java:320)
The problem happens when there's a Next-Gen issue type associated with the GreenHopper (Jira Software) project template. Since the issue type is restricted to the project scope, Jira is unable to proceed with the project creation.
Workaround
Contact support as it is necessary to remap the issue type back to the classic project
