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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation for Jira comment to customer triggers 1st response SLA Edited

Hi, I believe this is a similar question as this but there's no resolution.

I have an automation whereby 'Automation for Jira' comments to customer (and therefore public) to acknowledge the receipt of the ticket, giving guidance on other resources etc.

This in turn triggers the 1st response SLA, which effectively now only measures the speed of the Jira automation rule. I'd like to measure the first response by a human, e.g. the first comment to customer by the team, not 'Automation for Jira'. See screen grab below for 1st response SLA.

I wonder if we shouldn't be using an automation for jira to post the comment but rather an email notification feature to avoid this? If so, I'm unsure as to how to set this.

Bottom line, I need to track the 1st response SLAs, whilst providing a good service and acknowledgement to the customer. 

Any help is much appreciated.

Screenshot 2021-02-17 at 23.43.35.png

2 answers

Hi @Sif Rai,

Perhaps you can have a status between "New" (or the initial status of your request) and "Waiting for customer". For example, let's call it "Received".

On the Automation rule, you can transition the request to "Received" status and add a public comment during the transition.

On the SLA side, you should stop counting the SLA when the request goes into "Waiting for customer" status.

I hope that makes sense.

Thanks,
Moga

Many thanks Moga, please see my response to Brant below.

0 votes
Brant Schroeder Community Leader Feb 17, 2021

The issue is the SLA stops on the comment for customer, can you just remove this from the SLA and make sure that the status is changed when an agent comments to the customer?

Many thanks for your suggestion Brant, I had considered this and a similar option suggested by Moga above; we'd then need a specific status for 'responded' that would stop the SLA, and if it's resolved in the same response you'd then change the status again to 'done'.  

This to me feels a bit heavy handed, so I was after more of a solution utilising the built in notification features of Jira SD as opposed to utilising the Automation workflow rules. That way, Jira would send a 'received' notification email to the reporter without it being logged as a comment to customer. 

That's the same functionality as when you add someone as a request participant. We have that action configured to send a notification email to the person added. This is not shown on the ticket as 'comment to customer' but treated as a notification.

I'd expect the same function to be available for notification to reporter (e.g. acknowledgement of email received)?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

209 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you