Skip to main content

2 min read

Track and trace your scripts with ScriptRunner for Jira Cloud

Chirag Harendra
30 August 18 Jira
Track and trace your scripts with ScriptRunner for Jira Cloud
alert2 Icon
The content of this blog is no longer updated

Track and trace your scripts with ScriptRunner for Jira cloud

Make compliance your best friend with two new features in ScriptRunner for Jira Cloud; Execution History and Audit Log.


Have you have ever had to check through hundreds of tasks in ScriptRunner manually and just when you thought you had got to grips with it all, the start of the next week comes around and blind panic set in as you struggle to remember whether you enabled that escalation service on Friday evening or not?

If you can relate to this experience, you are not alone.  It can be a mammoth task to keep track of all the scripts you have running in ScriptRunner, and it can be even trickier to identify which of them have been executed successfully or not.

Stay compliant

To ensure greater tracking and monitoring capabilities and to stay compliant, several of our customers asked us to create a feature in ScriptRunner for Jira Cloud, that would enable them to view the history of their executed scripts including if they succeeded or failed.  

And so we created 'Execution History'; which allows you to view all scripts executed under a particular script category e.g. Scheduled Job and gives you the flexibility to access your historical data in graph or table format, and use the filter function to display the number of scripts executed over the previous three days.

Let's take a look at an example escalation service in action. Here we have a script that checks whether a task is closed at 3pm on a daily basis (except Saturday).

image2018 7 4 15 19 13

Check script execution status

If you would like to see whether your script executed successfully or not, you can now head to the new 'Execution History' section in ScriptRunner. Here you can access a tabular view of the date and time the Escalation Service was executed, including whether it was successful, who ran it, which issue it belongs to, and how long it took to execute.

image2018 7 4 15 23 10

Let's see how you can view this data in a graphical format. 

image2018 7 4 15 25 18

Deep dive reporting

What's more, if you need more detail on your executed scripts you can dig more-in-depth with our new 'Audit log' feature.

The Audit Log enables you to keep track of each action performed in ScriptRunner, whether it is a new script, or if it has been edited or removed and how long it has taken to execute. Together with Execution History, this provides you with an end-to-end reporting capability, to help you keep track of all your tasks and activities in ScriptRunner for JIRA Cloud.

The following image shows how you can view your data using the Audit Log feature, including a timestamp of when the event occurred, the name of the user who created it, the event itself, and any further details about it.

Audit Log SR Cloud

Want help creating your custom solution?

At Adaptavist we are always looking for the best ways to solve your most critical problems and to bring you great features to make your working life that bit easier. ScriptRunner solves different problems for different people, so if you are looking for guidance, advice or a little bit of support to get started and create your own custom ScriptRunner solution then help is at hand. 

copy_text Icon