Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Inherit SLA from parent issue?


Is there an ability currently for the sub-task issue to inherit the SLA values from the parent issue?

This is for the Time to SLA app from Snapbytes.

2 answers

1 accepted

1 vote
Answer accepted
Tuncay Senturk Community Leader Jan 16, 2019

Hello Michael,

Sorry that we missed this question.

Currently, there is no such a feature. You can only inherit linked issues' SLA values.

However, this may be a promising feature and Snapbytes team would like to develop it if you raise a support ticket here.



Hi @Tuncay Senturk 

From your answer: "You can only inherit linked issues' SLA values.".
This seems like exactly what I am looking for. Can you perhaps elaborate on "how"? Should the linked ticket just inherit the values from the original ticket automatically at the point when you create the linked ticket? In my case it creates a linked ticket with a new SLA timer value, rather than inherit the actual current timer value from the original ticket.

For example:
1. Create Ticket-1. The SLA timer starts at 60 minutes.

2. Wait 10 minutes. Ticket-1's timer is now at 50 minutes.

3. Create linked ticket, Ticket-2. The SLA timer  for Ticket-2 is set at 60 minutes by Jira, and not 50 minutes as I expected, if it were inheriting the values.

I expected Ticket-2's SLA time to start at 50 minutes at point of creation of Ticket-2, i.e. that 10 minutes has already elapsed because it is expected to inherit the timer value from Ticket-1, which had run down to 50 minutes.

Tuncay Senturk Community Leader Oct 30, 2021

Hi @I_Ponder 

Here, you can find how to achieve that using the customfields of Time to SLA.

You will find a checkbox "Display SLAs of Linked Issues" when defining the custom field.

Thanks so much for the info and quick response. I am hunting for a solution in the cloud space where have recently migrated to, but this does give me some great ideas and hopefully I can "take it from here". 

Really appreciate the feedback!

Tuncay Senturk Community Leader Oct 31, 2021

I'm happy to say that all features will be ready for the cloud very soon.

0 votes

Hi @Michael Schultz 

If you don't want to wait you can consider other solutions from the Atlassian marketplace. For example app SLA Time and Report has such feature you are asking for. There is a Linked Issue condition in the configuration menu. So you can choose a specific issue and when the issue has it as Linked, the SLA will trigger.

This add-on is created by my team, so let me know if you have any questions.

Best Regards

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events