Hi Pete, an SLA is only going to show for the issue it has been calculated for. SLAs are calculated for each issue independently, so since the subtask may not have had the same creation date as the parent it's not possible to put an SLA on it that will line up with the parent. There may be a plugin out there to do what you want, (or this might be a good idea for a developer to write one.)
Keep in mind the original design for SLAs was to set timers for individual user requests so a support team can support them in an agreed upon timeline. Subtasks are more of an older Jira Core concept and aren't really used in conjunction with SLAs. One thing you might want to consider as an alternative to subtasks is the creation of an Epic for user requests that are going to require extensive work. This will let you add an SLA to the Epic and then include issues from potentially different projects under the umbrella of one Epic. We've been able to use Epics successfully even in service desk projects without any problems.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.