Troubleshooting missing event types in workflow errors in Project Configurator for Jira

Owned by Yoga Reddy, created
Last updated: Sept 03, 2024 by Stanley Neychev
2 min read

 Problem

When running the Object Dependencies Report in Project Configurator for Jira, users encounter two errors without sufficient details to understand the underlying issues.

 Solution

Scenario 1:

This article provides step-by-step instructions to troubleshoot and resolve these errors.

[Project TEST] [Workflow scheme TEST: Workflow Scheme] [Workflow TEST: Workflow] (where TEST is the Project Name. Workflow scheme TEST and Workflow TEST are Workflow for the Project Test ) :

2024-06-11 14:06:02,349-0400 JiraTaskExecutionThread-47 ERROR thailey [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project TEST] [Workflow scheme TEST: Workflow Scheme] [Workflow TEST: Workflow] : java.lang.IllegalArgumentException: No event type with id 10800 at com.atlassian.jira.event.type.DefaultEventTypeManager.getEventType(DefaultEventTypeManager.java:83) at com.awnaba.projectconfigurator.jiraobjectfacades.EventTypeToolsImpl.getEventTypeFromId(EventTypeToolsImpl.java:43) at com.awnaba.projectconfigurator.extensionpoints.impl.TranslatorFactoryImpl$9.find(TranslatorFactoryImpl.java:752) at com.awnaba.projectconfigurator.extensionpoints.impl.TranslatorFactoryImpl$9.getExternalValue(TranslatorFactoryImpl.java:763) at com.awnaba.projectconfigurator.extensionpoints.impl.TranslatorFactoryImpl$9.getExternalValue(TranslatorFactoryImpl.java:1) at com.awnaba.projectconfigurator.extensionpoints.impl.IgnoreBlankValueTranslator.getExternalValue(IgnoreBlankValueTranslator.java:55) at com.awnaba.projectconfigurator.extensionpoints.impl.IgnoreBlankValueTranslator.getExternalValue(IgnoreBlankValueTranslator.java:1) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator$2.process(WorkflowTranslator.java:119) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator$NodeAction.doSomethingOn(WorkflowTranslator.java:261) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator.processExtensionsAsDoc(WorkflowTranslator.java:193) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator.processExtensions(WorkflowTranslator.java:180) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator.processExtensionsExport(WorkflowTranslator.java:134) at com.awnaba.projectconfigurator.adapters.workflow.WorkflowTranslator.makeInstanceIndependent(WorkflowTranslator.java:74) at com.awnaba.projectconfigurator.projectconfigserialize.WorkflowGlobalTable.makeContentsInstanceIndependent(WorkflowGlobalTable.java:44) at com.awnaba.projectconfigurator.projectconfigserialize.WorkflowGlobalTable.insert(WorkflowGlobalTable.java:63) at com.awnaba.projectconfigurator.projectconfigserialize.WorkflowGlobalTable.insert(WorkflowGlobalTable.java:1) at com.awnaba.projectconfigurator.projectconfigserialize.AbstractGlobalTable.lambda$0(AbstractGlobalTable.java:76) at com.awnaba.projectconfigurator.utils.SmartErrorReporter.wrapSafely(SmartErrorReporter.java:98)

How to fix Missing Event Types in Workflow TEST:

  1. Export the Workflow as XML:

    1. Navigate to Administration > Issues > Workflows

    2. Select the relevant workflow and click on Export as XML

    3. Exporting Workflows Documentation

  2. Identify and Update Missing Event Types:

    1. Open the exported XML file in a text editor.

    2. Search for <arg name="eventTypeId">10800</arg>.
      Note: The event TypedID 10800 mentioned above will be as per the instance. We have shown 10800 references.

    3. Identify transitions referencing the missing event type and update them with valid event types.

    4. Jira Event Types Documentation

Scenario 2:

  1. [Project TEMP] [Service desk TEMP] Trying to export com.onresolve.jira.groovy.groovyrunner:Behaviour mapping-service desks found problem: The request type you are trying to view does not exist.

    2024-06-11 14:06:04,163-0400 JiraTaskExecutionThread-47 ERROR thailey [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project TEMP] [Service desk TEMP] Trying to export com.onresolve.jira.groovy.groovyrunner:Behaviour mapping-service desks found problem: The request type you are trying to view does not exist. com.awnaba.projectconfigurator.utils.errorhandling.UnexpectedJiraProblemException: The request type you are trying to view does not exist. at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Unknown Source) at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source) at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83) at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250) at com.awnaba.projectconfigurator.utils.groovy.reflection.ReflectionUtils.processEither(ReflectionUtils.groovy:315) at jdk.internal.reflect.GeneratedMethodAccessor12609.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source)

     

  2. Fix the request type you are trying to view, which does not exist.

    1. Navigate to Script Runner Behaviours:

      1. Go to Administration > Script Runner > Behaviours

      2. Script Runner Behaviours Documentation https://docs.adaptavist.com/sr4jc/latest/features/behaviours

    2. Identify and Remove Unavailable Request Types:

      1. Locate the behaviours associated with the Service Desk PT project.

      2. Identify any behaviours linked to request types that no longer exist.

      3. Remove these behaviours from the project.

The issues were resolved by followi‍‍‍ng the above steps to identify and remove missing behaviours and update workflow transitions. The Object Dependencies Report was successfully run without errors.