You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.
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.