Bottom Tabs

Owned by Jonathan Muse
Last updated: Nov 20, 2024
3 min read

Editor Console

The editor console is an invaluable component that allows you to display output from a script in order to check the values of variables while debugging a script, or to display the progress and output of the script.

With some types of script errors an error message will be displayed in the console window. Some of these errors may only be visible in the console output or the log file output. For example, if while using one of the many file functions the path to the file is incorrect or the file does not exist, the script will result in an error and yet the syntax of the script may be completely correct so running the syntax checker would not have prevented the error.

Output can be intentionally displayed in the console by using either the “return” statement at the very end of the script, or the runnerLog() function anywhere within the script. Another useful feature of the console is that with the runnerLog() function you can make the console display HTML. In the simple example below an HTML table is output to the console.

New in Power Scripts 5.8.0.x, you can download the output of the console directly to a file. This is extremely helpful when using the console to export data from Jira. For example, you could export a list of all the inactive users in Jira and export the list from the console.

Server Log

Another useful feature at the bottom of the SIL Manager is the Server log viewer. This tool shows the contents of the actual Jira log file from the file system. This is helpful to debug scripts that appear is if they are working yet the results are not as expected.

 

Additionally you can use the log settings icon to search for key words in the log file or control how many lines are returned at a time.

Event Viewer

New in Power Scripts 5.8.0.x is the event viewer. The Event Viewer temporarily keeps records of actions and events within the SIL Manager. For example, if you ran a code check multiple times and wanted to compare the results from the previous run you could use the records located in the event viewer for this purpose.