-
Bug
-
Resolution: Fixed
-
Medium
-
5.12.0, 5.12.2, 5.12.4, 5.12.7, 5.13.0, 5.14.0
-
None
-
3
-
Severity 2 - Major
-
24
-
Issue Summary
The condition (groovy-script) that can be added within the post function "Create an Assets Object from a Jira Issue" will not be saved.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Edit any issue workflow
- Add a post function to any transition
- Select Assets Post-Function
- Select Create an Assets Object from a Jira Issue
- In the Condition field enter any groovy script
- Fill other fields as needed
- Click on Update
- Verify the data has been saved by clicking on the pencil icon of this post function
Expected Results
The groovy script has been saved and can be modified.
Actual Results
The condition field is empty. However, the script has been saved in the database
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
However, as the condition is saved, the workflow should work as expected.
You can check this by exporting the workflow as XML. After the export open the file in an editor and search for
<arg name="field.groovyCondition">
The groovy script will be noted after this. NOTE: depending on your workflow, you might have more than one groovy script, you will need to check each occurrence.