JiBrok Studio for Jira CloudInstallation
- Go to the Atlassian Marketplace and search for JiBrok Studio for Jira Cloud
- Click Install and select your Jira Cloud site
- Once installed, the app appears in the Jira top menu under Apps > JiBrok Studio for Jira Cloud
Note: JiBrok Studio for Jira Cloud is available to Jira administrators only. Non-admin users cannot access the app.
Navigate to the app
Open the Jira top navigation bar and click Apps > JiBrok Studio for Jira Cloud. The Console tab opens by default with an empty editor.
Your first script
1. Write a Script
Type the following into the editor:
log("Hello from JiBrok Studio for Jira Cloud!")
const now = new Date()
log("Current time:", now.toISOString())
// The last expression becomes the script result
"Script completed successfully"
2. Run It
Click the Run button (or use the keyboard shortcut). You will see:
- The output panel shows log messages
- The result field shows the value of the last expression
3. Run with Issue Context
Enter a Jira issue key (e.g., PROJ-1) in the Issue Key field, then run:
const issue = Issues.get(issueKey)
log("Issue:", issue.key)
log("Summary:", issue.summary)
log("Status:", issue.status)
issue.summary
The issueKey variable is automatically available when you provide an issue key.
Key concepts
Script isolation
Scripts run in a secure sandbox with strict limits:
- No network access - except through
requestJira()and built-in functions (Issues, Users, Projects, etc.) - No filesystem - scripts cannot read or write files
- Resource limits - execution time, loop iterations, and API calls are capped. Limits vary by trigger type. See Limits for details.
- Safe methods only - scripts can only use a curated set of approved operations
- Auto-await - async API calls are automatically resolved
Output
Use log() to print values to the output panel:
log("text") // simple text
log("a", "b", "c") // multiple values (space-separated)
log({key: "value"}) // objects are JSON-formatted
Other log levels: debug(), info(), warn(), error() - they appear with different styling in the output.
Result
The result is the value of the last expression in your script, or the value passed to return:
// Implicit result (last expression)
2 + 2
// result: 4
// Explicit return
return "done"
// result: "done"
Sandbox mode
Toggle Sandbox Mode to test scripts that make changes without actually modifying Jira data. Write operations (POST, PUT, DELETE) are simulated and logged.
Save to library
Click Save to persist your script to the Library:
- Set a name (required)
- Add an optional description
- Choose a folder location
- Assign labels for organization
Saved scripts appear in the Script Library and can be accessed from any session.
Based on your goal
| I want to… | Start here |
|---|---|
| Automate repetitive tasks | Triggers - attach scheduled or event-based triggers |
| Create computed fields | Scripted Fields - Text, Number, Date, DateTime |
| Customize issue forms | UI Modifications - hide/show fields, set defaults |
| Process issues in bulk | Scenarios - split bulk operations into managed steps |
| Store custom data | Data Storage - Custom Tables and Message Queues |
| Add Jira Automation actions | Automation integration - run scripts from Automation rules |
| Validate workflow transitions | Workflow Validator - block invalid transitions |
| Receive external webhooks | Webhook Trigger - trigger scripts via HTTP |
