-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Automation - Playbooks
-
None
-
1
Current Situation
When Playbook steps run on JSM tickets, the execution history (who ran which step, when, and the output) is only accessible in two places:
- The Playbook panel on the issue itself (no bulk export, and resets if the playbook is modified)
- The Automation audit log (subject to retention limits - currently 180 days max)
Problem
For compliance, auditing, and operational review purposes, customers need to retrieve a record of which Playbook steps were executed on tickets older than 180 days.
Use case
- A regulated organisation needs to prove which remediation steps were followed during an incident that occurred > 6 months ago.
- An IT team wants to audit SOP adherence across historical tickets for a quarterly review.
Amongst others...
Suggested improvement
Allow playbook execution logs to be exported via CSV and/or API at any time (no time limit).
Workaround
None.