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

Workflow Scheme with Bad Workflow Cannot be Disassociated from Project

XMLWordPrintable

    • 4.04
    • Severity 2 - Major
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      A workflow scheme that uses a "bad workflow" (contains Status ID error introuduced via XML import) cannot be unhooked from a project. The "Actions Cog" is missing from the workflow tab so it's not possible to switch to a different scheme and undo the damage.

      The bad workflow cannot be deleted because it is active.
      The workflow scheme cannot be edited or deleted because it is active.

      There are three fixes, all rather extreme:

      1. Roll back: restore JIRA from back-up
      2. Make changes to the JIRA database to edit the Status ID
      3. Delete the project & then re-import the XML workflow after fixing the Status ID there.

      I believe that it's a defect that there is no way to switch to a different workflow scheme.

      Background:

      An XML workflow that has been massaged to contain good "fieldscreen.id" can be imported into JIRA without generating an exception on import.

      However, if the XML contains an invalid "status.id" then the import will appear to succeed without problems.

      If the workflow is then associated with a workflow scheme and that scheme associated with a project then an exception will display on-screen when viewing the workflow tab for the project admin:

      Error rendering WebPanel (workflows/workflows.vm): org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in class com.atlassian.jira.web.component.IssueConstantWebComponent threw exception java.lang.NullPointerException at workflows/workflows.vm[line 136, column 65]

      From atlassian-jira.log:

      2012-05-11 14:01:18,815 http-8080-13 WARN marks 841x388766x1 17d4esl 192.168.150.57 /plugins/servlet/project-config/TST/workflows [plugin.web.model.ResourceTemplateWebPanel] Error rendering WebPanel (workflows/workflows.vm): org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in  class com.atlassian.jira.web.component.IssueConstantWebComponent threw exception java.lang.NullPointerException at workflows/workflows.vm[line 136, column 65]
com.atlassian.templaterenderer.RenderingException: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getHtml' in  class com.atlassian.jira.web.component.IssueConstantWebComponent threw exception java.lang.NullPointerException at workflows/workflows.vm[line 136, column 65]
	at com.atlassian.templaterenderer.velocity.one.six.internal.VelocityTemplateRendererImpl.render(VelocityTemplateRendererImpl.java:100)
	at com.atlassian.templaterenderer.AbstractVelocityWebPanelRenderer.render(AbstractVelocityWebPanelRenderer.java:33)
	at com.atlassian.plugin.web.model.ResourceTemplateWebPanel.getHtml(ResourceTemplateWebPanel.java:47)
(snip..see attached log)

      Note Also:

      There might be two other issues here..

      1. The XML import should check Status ID
      2. Integrity Checker should check Status ID. This is what it gives currently when there is a workflow with a broken Status ID:

      Check Workflow Integrity
      PASSED: Check workflow entry states are correct
      PASSED: Check workflow current step entries
      PASSED: Check JIRA issues with null status

        1. workflows_vm-exception.txt
          16 kB

              Unassigned Unassigned
              2f113cc8540a Mark Symons
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: