Thanks everyone for your feedback. After consideration, we are closing this issue because we do not expect to address it in the foreseeable future. As is clear from the examples below, the ideal propagated action depends on the type of issue link and varies depending on your use case. Considering issue links can be arbitrarily defined, this would require adding logic in JIRA to handle certain types of links differently from others. Alternatively, we would need to add settings to configure propagated actions based on the issue links.
Our belief is that the value doees not justify the expected increase in UI complexity or maintenance burden.
As always, please don't hesitate to contact me if you have any questions.
Product Manager, JIRA Platform