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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,556,456
Community Members
 
Community Events
184
Community Groups

[SOLVED] Automation for "Time to resolution" does not working well

Edited

Hi,
I have implemented an automatism which, when the "Time to resolution" SLA changes, must send an email to reporter.

The email is sent to reporter, but it does not receive the SLA.

Could you tell me if there is something wrong with this rule:

"Gentile utente,
il ticket {{issue.key}} verrà risolto entro il {{issue.Time to resolution.ongoingCycle.remainingTime.friendly}} salvo imprevisti.

"

{{issue.type}} returns the ticket number

{{issue.Time to resolution.ongoingCycle.remainingTime.friendly}} returns an empty value

------------------------------

This automatism works on a test instance, on the client instance it doesn't work.

Could this be a problem with the SLA calendar?

 

Calendar 1 is: Default calendar 24/7

Calendar 2 is customized:

Immagine 2023-05-18 102315.jpg

 

 

Thank you

Marco

2 answers

Problem solved:

if you have only one custom field with the name Time to Resolution, use this:

{{issue.Time to Resolution.ongoingCycle.goalDuration.friendly}} - time goal of the TTR SLA
{{issue.Time to Resolution.ongoingCycle.elapsedTime.friendly}} - elapsed time of the TTR SLA
{{issue.Time to Resolution.ongoingCycle.remainingTime.friendly}} - remaining time of the TTR SLA

if you have more custom field or more values for Resolution, use this:

{{issue.customfield_xxxxx.ongoingCycle.goalDuration.friendly}} - time goal of the TTR SLA
{{issue.customfield_xxxxx.ongoingCycle.elapsedTime.friendly}} - elapsed time of the TTR SLA
{{issue.customfield_xxxxx.ongoingCycle.remainingTime.friendly}} - remaining time of the TTR

0 votes
Kateryna_v_SaaSJet_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 26, 2023

Hi @Marco Savarese 
What do you mean under "it does not receive the SLA."?
Are you talking about SLA report or SLA name?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events