Issue Summary

Attempting to delete Sub-tasks results in errors and an incorrect search index.

The effect is inconsistent. If there is only one sub-task it will be deleted fairly reliably.
Sometimes one or more subtask in a group will be deleted. When there are ~30 subtasks it fails to delete any subtasks consistently.

Steps to Reproduce

1. Add 5+ subtasks to an issue.
2. Create a rule with a manual trigger and a "For Sub-tasks" branch rule.
3. In the branch rule, add the "Delete Issue" action.
4. Trigger the rule from the More menu

Expected Results

• All sub-tasks deleted and no longer visible on the parent issue.
• Searching for parent=PARENT_ISSUE_KEY returns no results.

Actual Results

• Sub-tasks are not deleted and are still visible in the parent issue.
• Searching for parent=PARENT_ISSUE_KEY returns no results.

If I modify the Summary of one of the sub-tasks (which reindexes it) this sub-task will re-appear in search results.

In the instance where this was observed, SQL exceptions appear in the audit log for the rule.

Caught PSQLException for update public.issuelink set sequence = ? where issuelink.id = ?

or

org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT pkey, issuenum, PROJECT, REPORTER, ASSIGNEE, CREATOR, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, WATCHES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT, ARCHIVED, ARCHIVEDBY, ARCHIVEDDATE FROM public.jiraissue WHERE ID=? (ERROR: current transaction is aborted, commands ignored until end of transaction block)...

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available