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

Access Incident Summary from a Post Incident Review using Automation

Summary

Within a Post Incident Review, there is a section above the SLAs where a linked Incident will show values such as:

  • Incident created
  • Incident ended or ongoing
  • Time to resolution
  • Incident assignee
  • Incident responders
  • Affected services

However, how do you access this information where these values can be used elsewhere, such as a form on a PIR? This would be through Automation for Jira using Smart Values

Configuration Example

In the example shown in the screenshots below, I used a Manually Triggered Rule for testing with the "Add value to the Audit Log" action to ensure the values that were filled in would populate when called in using smart values. Those Smart Values would be:

Incident Created: {{triggerIssue.issuelinks.outwardIssue.created}}  

Incident Ended: {{triggerIssue.issuelinks.outwardIssue.resolutionDate}} 

Time to Resolution: {{triggerIssue.issueLinks.outwardIssue.customfield_10050.completedCycle.friendly}}  

Incident Assignee: {{destinationIssue.issuelinks.outwardIssue.assignee.displayName}} 

Incident Priority: {{triggerIssue.issuelinks.outwardIssue.priority.name}} 

Incident Responders: {{triggerIssue.issuelinks.outwardIssue.responders.name}}

Affected Services: {{triggerIssue.issuelinks.outwardIssue.affectedServices}}

Please note that the Time to Resolution field will only populate for completed Time to Resolution SLAs, not ones that are in an ongoing cycle. Please see the screenshots below for the example Incident Summary with the Automation Rule and Smart Value data passed into the Audit Log of the Rule.

Supporting Screenshots

Screenshot 2023-08-30 at 7.10.16 AM_2023-08-30T14_10_44.870Z.pngScreenshot 2023-08-30 at 7.10.29 AM_2023-08-30T14_10_44.870Z.png

I hope this helps!

 

Cheers,

Christian B.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events