- Overview
- Who sees the panel
- Linked scripts
- Execution history
- What is recorded
- Linking scripts to issues
- Messages
- Next steps
Overview
JiBrok Studio adds a Studio Log panel to the Jira issue view. It shows which scripts ran on the issue and which scripts are linked to it, without leaving the issue.
Who sees the panel
- The panel is shown only to Jira administrators. Other users do not see it on the issue.
- It needs an active app license; without one the panel shows the license warning instead of data.
- Open it from the issue view’s app context area: the panel title is Studio Log; while the panel is collapsed, Script runs follows the title. The open panel does not repeat the title above its sections.
Linked scripts
The Linked Scripts section lists scripts that mention this issue (see Linking scripts to issues). Each name is a link that opens the script in the Script Console in a new tab. Deleted scripts are not listed.
Execution history
Below the linked scripts, the panel lists script runs recorded for the issue, newest first, under a refresh button:
| Element | Description |
|---|---|
| Icon | Green check - Success, red cross - Error |
| Script name | Link that opens the script in the Console in a new tab; (deleted script) when the script no longer exists. In a narrow panel a long name is cut at the panel edge |
| Time | Relative time (45s ago, 12m ago, 3h ago, 2d ago) on one line at the right of the row; hover for the full date and time |
- 10 entries are shown at first; Show more loads the next 10.
- The refresh button above the run list reloads both sections.
The list combines two sources:
- the history stored on the issue by the daily issue tracking sync (up to 400 most recent entries per issue), and
- runs recorded since the last sync and still waiting for it.
So a new run appears in the panel right away, even before the daily sync writes it to the issue.
What is recorded
Entries come from issue tracking, which is on by default and configured in Admin Panel - Admin - Issue Tracking (Enable issue execution tracking, Daily sync hour, default 3, in the site timezone). See Service Project Integration - Issue tracking for the stored format and JQL searches.
An entry is recorded:
- for the issue a script ran for (the run’s issue key - for example a Console run with an issue key, an event, workflow or automation run on an issue), whether or not the script changed it, and
- for every other issue the script created, updated, transitioned or deleted through the Jira REST API, including adding comments, worklogs or watchers.
Not recorded:
- runs in Sandbox mode,
- scripted field calculations and UI modification (UIM) runs,
- anything while issue tracking is switched off.
Linking scripts to issues
A script is linked to an issue automatically when the issue key (for example PROJ-123) appears:
- in the script’s Description - links follow the description: when you edit it, keys that are no longer mentioned are unlinked;
- in a version note entered when saving the script - these links are kept when the description changes (see Version History).
The Config tab of the script shows its links under Issue Links (“Issue keys mentioned in the description or version notes are automatically linked”), each opening the issue. In the Script Library, a script row shows up to three linked keys and a +N counter, and the Filter by issue… field finds scripts linked to an issue.
Limits and notes:
- Up to 20 linked issues per script; further keys are ignored.
- Keys are taken as written; the issue does not have to exist. Links whose issue was deleted can be cleaned up with the Data integrity check in Admin Tools - Health check.
- Folder, queue and custom API whitelist / blacklist descriptions are linked the same way, but the issue panel lists scripts only.
Messages
| Message | Meaning |
|---|---|
| No script executions recorded for this issue. | Nothing recorded and no linked scripts |
| Failed to load execution history. | The history could not be loaded; use refresh or reopen the issue |
Next steps
- Service Project Integration - Issue tracking settings, issue property format and JQL
- Script Console - Run History of a script
- Script Library - Filtering scripts
- Version History - Version notes
