THIS DECISION HAS BEEN ARCHIVED and replaced by Data consistency and message driven approach. While the examples here may be illustrative and useful for gaining additional context, no further discussions or decisions should take place here.

...

Page Properties
Status Status colour Green title COMPLETE Stakeholders Front-end and back-end devs of non-core modules that hold references to records in core-modules Outcome UI modules    Created date 17 Mar 2021   Owner Zak Burke

Note
title NOTICE
This decision has been migrated to the Technical Council's Decision Log as part of a consolidation effort.  See:   DR-000024 - Deletion of core-module records may leave dangling references from non-core modules

Context

• Deletion of records by core UI modules is problematic because it may leave dangling references to deleted records in non-core modules. Core modules are at the bottom of the hierarchy, unaware of the modules that sit above them in the hierarchy; this prevents core modules from issuing queries to identify such references. This is succinctly, if frustratingly, captured in the PR discussion related to UITEN-128.
• Even if we can resolve this in the UI (see notes, below) the possibility remains that direct API requests to delete records may leave dangling references in other parts of the system.

...

JIRAs

• Jira Legacy
  server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UITEN-128

• Jira Legacy
  server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UITEN-74

• Jira Legacy
  server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UITEN-75

• Jira Legacy
  server System JiraJIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICR-125

...

It worth also noting that

Jira Legacy
server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UICR-125

case is slightly different and is about dangling references while not deletion but moving of a core-module record; neither cascade nor soft deletion is applicable here. At the same time, this case and cascade deletion case have one great similarity - in both, non-core-modules are to be notified about a change in core-module. In this context, a robust notification channel with guaranteed delivery to transfer change events from one module (say, module-source) to another module (say, module-recipient) is required.  More details are on Data consistency and message driven approach # Notification channel.

...