Jira automation you can actually see

Scriptline is a Jira Cloud app for writing automation in TypeScript or JavaScript instead of a proprietary scripting language. Scripts run from an in-product console, automatically on work-item events, on a schedule, behind a JQL function, as a computed field or as background bulk jobs, and every run records its logs, timing, result and line-numbered errors so automation never fails silently.

Yes. Scriptline covers the core ScriptRunner for Jira Cloud workflow: event listeners, scheduled jobs, bulk operations, JQL functions, a scripted field and an ad-hoc console. It adds replayable run records, automatic versioning with rollback and dry-run. It is built natively on Atlassian Forge with zero external egress, so scripts never leave Atlassian's infrastructure.

Ten kinds: work item created, updated, deleted and assigned; comments; worklogs; links; attachments; and project version changes. Each listener can be scoped to specific projects, work item types or (for updates) specific changed fields, picked from your Jira rather than typed by hand.

Yes. Describe the schedule in plain words, such as every 15 minutes, every weekday at 09:00 or monthly on day 1, and the builder writes the cron for you, previewing the next three runs in your local time. Custom cron is available too. Schedules are checked every five minutes.

TypeScript or JavaScript. No Groovy and no proprietary language. Scripts get a small, typed Jira API (search, get, comment, update, transition, iterate) plus a generic escape hatch to call any Jira Cloud REST endpoint.

Write a script, give it a JQL, and Scriptline runs it once per matching work item in the background, so there is no browser timeout. You get live progress, per-item error samples and a cancel button, and dry-run is respected so you can rehearse first.

A toggle that suppresses every write to Jira (comments, updates, transitions) and logs what would have been sent instead. Reads run for real, so the log shows exactly what the script would have done. You can also simulate a work-item event from the console.

Yes, two ways. Eleven built-in functions with the names ScriptRunner users already know, such as linkedIssuesOf, subtasksOf and parentsOf, work in any search with no script at all. And issue in hooked("my-hook") runs a saved script of your own, which returns a JQL fragment or a list of work item keys. Broken queries return no matches instead of breaking your filter, and failures are recorded in Run history.

Yes. Scriptline adds a read-only custom field, Scripted field (Scriptline), whose value is computed per work item by your script. It shows on the work item view, is stored, and is searchable in JQL.

Not yet. Live form-field rules depend on Atlassian's UI-Modifications API, which is still maturing. Rather than ship a half-working version, Scriptline focuses on what it does well today. Behaviours-style rules are on the roadmap.

In Atlassian-hosted app storage tied to your Jira site, encrypted at rest by Atlassian: scripts, versions, run history and job records alike. The app makes zero external network calls: no vendor servers, no analytics, no third parties.

Jira administrators only. The app lives in Jira's admin settings, and every action independently checks that the caller holds the Administer Jira permission.

Scriptline is sold through the Atlassian Marketplace. Free for up to 10 users; US$2.13 per user per month for 11-100 users, tapering down automatically for larger sites, with a 30-day free trial on every paid tier.