How do I get the subtasks of a ticket to reflect the SLA of that of the parent ticket?

bunny
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 10, 2024

I have a parent task that is 56 hours overdue (show in SLA) but it has some attachments and I converted the name of the attachments to subtasks. Of course, because I created the subtasks today, it doesn't show that the subtasks are 56 hours are overdue as the parent ticket. Anyway to navigate this?

Sub-task SLA:

subtask sla.png

Parent issue SLA:

parentsla.png

 

Do I need to have admin access for this?

1 answer

1 accepted

1 vote
Answer accepted
Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 10, 2024

Hi @bunny , welcome to the Atlassian Community!

There is not a quick and easy way of doing this, as the SLAs are only triggered from the SLA settings.

I would also question the logic behind this decision. Subtasks should be used as a way of breaking down a parent task into smaller sections, and any SLAs on the parent task usually encompass all subtasks beneath it (I haven't seen this requirement to copy SLAs from the parent to subtasks very frequently)...

If this is a firm requirement however, you may be able to do this through some custom automations - e.g. If your subtasks used the same workflow as the parent, you could create automation rules which sync the subtask statuses whenever the parent is transitioned, which would then also act as the trigger for the SLA (assuming your subtask issue types fall within the JQL in the SLA settings).

Hope this helps!

 

Callum Carlile _Automation Consultants_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 10, 2024

Ah apologies I've just seen you've edited your original question.

For this requirement, you could create an automation which copies the SLA remaining on the parent into a custom field on any newly created subtasks. This custom field could then be used within the JQL in the SLA settings that would trigger when your subtasks are created - though you would need to create 'batches' of JQLs within your SLA settings, e.g:

custom field <2h
custom field >=2h and < 4h
custom field, custom field >=4h and < 6h
etc.

Like bunny likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events