A problem we currently have to workaround is the fact that we sometimes log high-level features that we then split into many smaller tasks, which we then link using a "subtask" link. I'm certain many companies do something similar.
The problem is that since for JIRA links are meaning-less, effort estimated on the high-level task won't be kept up-to-date with the effort involved in subtasks, etc.
In order to workaround this problem we have to specify quite a complex procedure for our developers.
If instead JIRA detected (or defined) this "subtask" links between issues, it would know it needs to add/substrack effort accordingly, etc.. and it would save developers & managers the effort.
|Modify Time Tracking report to include aggregate time information||Resolved||
|Modify Version Workload Report to include subtasks with fix-for set to other versions||Resolved||Unassigned|