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

JIRA does not load workflow components (functions, conditions, validators) from the core libraries

    XMLWordPrintable

Details

    Description

      When fixing JRA-20528 a new way of loading workflow component was introduced. It relies on those components being registered as plugins. It prevents usage of any such components defined in core JIRA libraries, e.g. by loading a custom workflow XML. Examples:

      • BeanShellCondition from OSWorkflow
      • UberIssueWorkflowFunction from JIRA core

      This also makes JIRA 4.1.2 incompatible with previous versions and may cause problems during upgrades of instances with custom workflows.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-22397 DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found

          • Medium - Medium priority issues
          • Closed
          is caused by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-20528 Workflow plugin modules defined in V2 plugins will sometimes not work

          • High - High priority issues
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-23512 Undocumented dropped support for built-in OsWorkflow components in JIRA 4.1.2

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              dkordonski Dariusz Kordonski (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: