Activity and Run History
Check when configurations ran, read their logged output, and diagnose failures.
Every feature records activity in the same way, so you only have to learn it once. Activity is the record of what actually happened: each run/execution, including any that failed, each publish, and the point at which the configuration was created.
Most configurations run in response to something happening in Jira, so activity is often the only way to confirm that a run took place. It is where you look when something did not happen, happened more than once, or ran but did not do what you expected.
Where to find activity
Activity appears in two places:
- On a feature page: The Activity column shows recent runs for each configuration at a glance.
- On a configuration: Open a configuration and select the status next to its title. This shows the last five changes, such as edits and publishes. Select View all activity to open the activity panel, which shows runs as well.
In the script console, activity is recorded when you test a script with Test script, and appears in the test panel rather than the activity panel. The test panel does not clear between runs: it keeps up to five runs from the last hour, with the run you just started opened for you, so you can compare a result against the one before it. If you save the script, its run history is kept with the saved script.
Read an Activity
Select an activity to see:
- When it started and how long it took
- What triggered it
- Anything logged with
console.log(...) - The value returned by your script with
return - The error, if the run failed, with the full untrimmed error behind Full error
- For a publish, which settings changed and what they changed from
Filter what you see
In the activity panel, use the filters at the top to narrow the list. Each one shows how many entries it has.
- All: everything recorded for this configuration.
- Published: only the times it was published.
- Runs: only runs, including any that are still queued or running.
- Errors: only the ones that need attention, which are publishes that failed, and runs that errored or logged with
console.error(...). Anything shown in red is included.