Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
6.9.1, 6.23.0
-
None
-
SR4C Sprint 161, SR4C Sprint 162, SR4C Sprint 165, SR4C Sprint 166, SR4C Sprint 167, SR4C Sprint 168, SR4C Sprint 169, SR4C Sprint 170
-
0.5
Description
Steps to Reproduce
Provide a detailed step-by-step process to reproduce the problem.
- Install an older version of Comala Document Management (e.g. 6.14.0.1) - you can download it from https://marketplace.atlassian.com/apps/142/comala-document-management/version-history
- Use a timebomb license for Comala - https://developer.atlassian.com/platform/marketplace/timebomb-licenses-for-testing-server-apps/
- Configure a space to use a workflow (the Simple Approval Workflow will do)
- Configure a Script Event Listener on a Comala Workflow event (such as the ApprovalEvent)
- Confirm that said Script Listener fires (such as by approving a page)
- Upgrade Comala Workflows (e.g. to 6.14.1)
Expected Behaviour
The listener should still fire.
Actual Behaviour
The listener does not fire.
Newly registered listeners on the same event may fire, though even this appears to be inconsistent.
Workaround
The only known workaround is to restart the Confluence server.
Disabling and re-enabling ScriptRunner does not make the listeners re-register correctly. Neither does clearing the Groovy caches using our built-in script.
Attachments
Issue Links
- is related to
-
SRPLAT-1700 Listeners for events from other plugins break on plugin upgrade or UPM upgrade
-
- Done
-
-
SRCONF-822 Comala workflow events occur twice
-
- To Do
-
- relates to
-
SRCONF-822 Comala workflow events occur twice
-
- To Do
-