Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

SLAs time doesn't change when the request type changes

I have different SLAs times depending on the request type. If I change manually the request type from a customer, the time to done remains the same.

1 answer

0 votes
Gaurav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 28, 2021

Hello @Jorge Vea 

In order to have different SLA for different request type, you need to define the JQL accordingly. I am using this for same issue type but different priority and it works fine. Please fine below the screen shot.

The JQL needs to be customized as per your requirements.

Let me know if this helps or if you have any other questions.

SLA.JPG

Yes, I have done that. The issue is when a customer generates an incident but is a request. So I change the request type (they got different SLA times) but the SLA remains the same and it should change as well as the type.

Gaurav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 29, 2021

Hello @Jorge Vea 

I understood the problem and was able to replicate it on my end. So, what is happening, once we have moved the issue from Incident to Service Category, the 'Request Type' value comes back as Empty or None, due to this the SLA values do not change.

This value needs to be updated, for the new SLA to be reflected. Please see the screen shots below for this.

Let me know if this helps or if you have any other questions.

Incident Ticket.JPG

Service Request.JPG

 

SR with SLA.JPG

If I update that value it doesn't change automatically the SLA time.

Gaurav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 29, 2021

Hello @Jorge Vea 

The updated SLA times reflected after a few minutes for me. Is it the same case with you or are the SLA times not updating at all?

No, the SLA times dont update at all... I dont know why.

Gaurav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 02, 2021

@Jorge Vea, Could you please share the screenshot for the SLA setup? This will help in understanding the issue.

Hi @Jorge Vea , 

How did you solve this issue I'm facing the same problem. 

I can confirm that the SLAs have been defined correctly for the request type because when you raise the ticket in the correct request type it calculates it as needed. 

Thanks in advance. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events