Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-65865

Import from Trello is bringing invalid workflow causing errors in JIRA

    XMLWordPrintable

Details

    Description

      Summary

      Workflows importing from Trello are causing severe problems in JIRA related to workflows:

      1. The statuses page gives a 500 error page and a stacktrace. The user is unable to change/view statuses
      2. No workflow is shown in the workflow page
      3. Navigation to a project's workflow page is showing this error:
        The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation.
        

      Stacktrace in the statuses page:

      Technical details
      Cause
      Referer URL: https://agilys.atlassian.net/secure/admin/ViewIssueTypes.jspa
      com.google.template.soy.tofu.SoyTofuException: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{param first: isFirst($status) /}{param last: isLast($status) /}{/call}{/foreach}, the data reference does not resolve to a SoyList (encountered type com.google.template.soy.data.restricted.UndefinedData).
      com.google.template.soy.tofu.SoyTofuException: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{param first: isFirst($status) /}{param last: isLast($status) /}{/call}{/foreach}, the data reference does not resolve to a SoyList (encountered type com.google.template.soy.data.restricted.UndefinedData).
      	at JIRA.Templates.Statuses.success(Unknown Source) [?:?]
      	at com.google.template.soy.tofu.internal.BaseTofu.renderMainHelper(BaseTofu.java:369) [?:?]
      	at com.google.template.soy.tofu.internal.BaseTofu.renderMain(BaseTofu.java:322) [?:?]
      	at com.google.template.soy.tofu.internal.BaseTofu.access$100(BaseTofu.java:66) [?:?]
      	at com.google.template.soy.tofu.internal.BaseTofu$RendererImpl.render(BaseTofu.java:476) [?:?]
      	at com.atlassian.soy.impl.DefaultSoyManager.render(DefaultSoyManager.java:151) [?:?]
      ...
      	at org.apache.coyote.ajp.AbstractAjpProcessor.process(AbstractAjpProcessor.java:831) [tomcat-coyote.jar:8.0.20]
      	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:659) [tomcat-coyote.jar:8.0.20]
      	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1558) [tomcat-coyote.jar:8.0.20]
      	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1515) [tomcat-coyote.jar:8.0.20]
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_45]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_45]
      	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:8.0.20]
      	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_45]
      Caused by: com.google.template.soy.sharedpasses.render.RenderException: In 'foreach' command {foreach $status in $statuses}{call .statusRow}{param status: $status /}{param first: isFirst($status) /}{param last: isLast($status) /}{/call}{/foreach}, the data reference does not resolve to a SoyList (encountered type com.google.template.soy.data.restricted.UndefinedData).
      	at JIRA.Templates.Statuses.success(Unknown Source) [?:?]
      	at com.google.template.soy.sharedpasses.render.RenderVisitor.visitForeachNode(RenderVisitor.java:384) [?:?]
      	at com.google.template.soy.soytree.AbstractSoyNodeVisitor.visit(AbstractSoyNodeVisitor.java:104) [?:?]
      	at com.google.template.soy.soytree.AbstractSoyNodeVisitor.visit(AbstractSoyNodeVisitor.java:56) [?:?]
      

      Steps to Reproduce

      1. Carry out an import from Trello with workflows (all conditions here are still unknown)

      Expected Results

      The workflows are correctly imported

      Actual Results

      The imported workflows break many pages.

      Notes

      Based on the errors and other issues we think the problem with the workflows is that they use 'action IDs' (the transition IDs) that were already used in different workflows.

      This cannot be correctly interpreted by JIRA and the pages break.

      Workaround

      Contact Support for a fix

      Attachments

        Issue Links

          Activity

            People

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              jsilveira Jaime S
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: