Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Medium
Fix Version/s: None
Affects Version/s: 4.1.2, 4.2
Component/s: Administration - Workflows, UPM (Universal Plugin Manager)
Labels:
- affects-server
- workflows

Introduced in Version:
4.01

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.

duplicates

JRASERVER-22397 DefaultOSWorkflowConfigurator.JiraTypeResolverDelegator should fall back to JiraUtils.loadComponent(objClass) to load the class if type resolver is not found

Closed

is caused by

JRASERVER-20528 Workflow plugin modules defined in V2 plugins will sometimes not work

Closed

relates to

JRASERVER-23512 Undocumented dropped support for built-in OsWorkflow components in JIRA 4.1.2

Closed

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

Created:: 25/Jan/2011 12:00 AM
Updated:: 28/Mar/2019 12:01 AM
Resolved:: 15/Mar/2011 12:13 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates