Subtasks Set to Null due to 'Field Issuetype No Issue Type Selected'

Symptoms

Search results in the Issue Navigator are erroring and not displaying any results. Errors like the following appear in your logs:

2009-06-10 08:10:32,258 http-443-Processor44 WARN [workflow.function.issue.TransitionSubtasksFunction] Field validation error auto-transitioning subtask CXM-957:
2009-06-10 08:10:32,258 http-443-Processor44 WARN [workflow.function.issue.TransitionSubtasksFunction] 	Field issuetype: No issue type selected.
2009-06-10 08:10:32,383 http-443-Processor44 WARN [workflow.function.issue.TransitionSubtasksFunction] Field validation error auto-transitioning subtask CXM-974:
2009-06-10 08:10:32,383 http-443-Processor44 WARN [workflow.function.issue.TransitionSubtasksFunction] 	Field issuetype: No issue type selected.

Cause

The Subtask Auto-transition plugin (Now Deprecated) is setting the Issue Type column in the jiraissue table to null.

Resolution

  1. Check if the transition screen that is being auto-transitioned contains issue type. If so, remove it.
  2. To find the issues that have already been set to null, run the following query in the database:

    SELECT
        jiraissue.pkey, jiraissue.issuetype
    
    FROM
        jiraissue
    LEFT OUTER JOIN
        issuetype
        ON
        (
            jiraissue.issuetype = issuetype.id
        )
    where issuetype.pname is null
    

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport