Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-7116

Using global transitions that uses the same name as another transition in JSM workflows fails to process automation rules

XMLWordPrintable

      Issue Summary

      When a workflow has a global transition that has the same name as another transition in that workflow will fail automation rules that uses those transitions.

      Steps to Reproduce

      1. Create a new workflow, or edit an existing workflow with a global transition that has From status "Any status" and To status "Itself"
      2. Use a name for an existing transition in the workflow
      3. Create an automation rule that uses that transition

      Expected Results

      Automation rule processes as intended.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      2021-02-15 14:09:27,873 PsmqAsyncExecutors-job:thread-18 WARN admin 671x329x1 11mg998 0:0:0:0:0:0:0:1 /secure/WorkflowUIDispatcher.jspa [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'java.lang.IllegalStateException - Duplicate key Mark as Done (fieldscreen)'.

      The automation rule log also displays an error has occurred.

      Workaround

      Rename the global transition to use a different name to the transition as specified in the log.

            [JSDSERVER-7116] Using global transitions that uses the same name as another transition in JSM workflows fails to process automation rules

            There are no comments yet on this issue.

              lbernardo@atlassian.com Lenard Bernardo (Inactive)
              lbernardo@atlassian.com Lenard Bernardo (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: