Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29630

Sub-Tasks Not Using Assigned Workflow When Moving Parent Issue To Another Project

    XMLWordPrintable

Details

    Description

      Pre-Conditions

      • Source project and destination project has custom workflows.
      • Custom workflows have custom statuses.

      Issue/Reported Bug

      When moving an issue with sub-tasks from one project to the next, the parent issue will use the destination project's workflow assigned to the set status. However, its sub-task(s) would not use the destination project's workflow, but uses the default jira workflow instead.

      On some occasions, insisting on moving the issue will spew out the following stack trace:

      java.lang.RuntimeException: No step associated with status In Progress (Task) in new workflow Deploy Workflow
	at com.atlassian.jira.workflow.OSWorkflowManager.migrateIssueToWorkflowNoReindex(OSWorkflowManager.java:528)
	at com.atlassian.jira.workflow.OSWorkflowManager.migrateIssueToWorkflow(OSWorkflowManager.java:488)
	at com.atlassian.jira.web.action.issue.MoveIssueConfirm.migrateIssueToWorkflow(MoveIssueConfirm.java:629)
	at com.atlassian.jira.web.action.issue.MoveIssueConfirm.migrateSubTask(MoveIssueConfirm.java:606)
	at com.atlassian.jira.web.action.issue.MoveIssueConfirm.moveSubTasks(MoveIssueConfirm.java:451)
	at com.atlassian.jira.web.action.issue.MoveIssueConfirm.doExecute(MoveIssueConfirm.java:284)
	at webwork.action.ActionSupport.execute(ActionSupport.java:165)
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82)
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39)
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31)
	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16)
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35)
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:221)
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:150)
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:153)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.atlassian.jira.web.filters.XContentTypeOptionsNoSniffFilter.doFilter(XContentTypeOptionsNoSniffFilter.java:22)
	at com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
...

      Workaround

      1. Convert the sub-task(s) to an issue.
      2. Move the converted issue(s) as well as the main issue to the destination project.
      3. Convert the converted issue(s) to sub-task(s) again.

      However...

      The workaround may not be feasible when dealing with the following scenarios:

      • an issue with lots of subtasks,
      • lots of issues with a subtask, or
      • lots of issues with lots of subtasks.

      Attachments

        1. destination-workflow.png
          destination-workflow.png
          41 kB
        2. moving-issues-status-select.png
          moving-issues-status-select.png
          32 kB
        3. source-workflow.png
          source-workflow.png
          52 kB

        Issue Links

          derived from

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-17312 The "Move" operation may produce subtasks with invalid empty values in target project

          • Medium - Medium priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JSWSERVER-8703 Attempting to Index with JIRA Agile(GreenHopper) enabled throws a UndeclaredThrowableException or a NullPointerException

          • Medium - Medium priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31734 NPE error when moving issue with subtask in case target project has a different workflow for the subtask

          • High - High priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              jalex Justin Alex [Atlassian] (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: