Quick Actions (Built-In Scripts) — User Manual & Partial-Failure Semantics

Quick Actions (Built-In Scripts) provide ready-to-use, parameterized bulk operations designed to help Jira administrators efficiently manage issues, custom fields, and workflows across projects without writing custom code.

---

Available Quick Actions

Action	Description	Key Parameters
Bulk Transition Issues	Transition matching issues through workflow states in bulk	JQL, Target Transition ID/Name, Comment
Bulk Delete Issues	Permanently delete issues matching a JQL filter	JQL Query, Confirmation Flag
Bulk Clone Issues	Duplicate issues matching a filter into a target project	JQL Query, Target Project, Prefix
Fix Resolutions	Set or update resolution fields on closed/resolved issues	JQL Query, Target Resolution
Copy Custom Field Values	Copy values between custom fields across issues	JQL Query, Source Field, Target Field

---

Partial-Failure Semantics & Transaction Safety

---

How Checkpointing & Resume Tokens Work

graph TD
    A[Start Bulk Quick Action] --> B[Initialize Execution Checkpoint in Storage]
    B --> C[Process Issues in Batches N=15]
    C --> D[Save Progress Checkpoint every 15 items]
    D -->|More Items| C
    D -->|Timeout or Interruption at Item 700| E[Status: PARTIAL_FAILURE / TIMED_OUT]
    E --> F[Persist Checkpoint: lastProcessedKey = PROJ-700, remaining = 1300]
    F --> G[UI Displays Partial Failure Alert & 'Resume Remaining' Button]
    G -->|User Clicks Resume| H[Resume Execution from Item 701 using Checkpoint Token]

1. Mid-Execution Checkpointing

As a bulk job processes items, ScriptFabric automatically writes checkpoint snapshots to storage every 15–20 items. Each snapshot records:

• total_items: Total number of issues matched by the JQL filter.
• processed_count: Number of issues attempted so far.
• succeeded_count: Number of successfully updated issues.
• failed_count: Number of failed issues with error messages.
• last_processed_key: Key of the last processed issue (e.g., PROJ-700).
• checkpoint_data: Map of processed issue keys and parameters required for resumption.

2. Itemized Audit Logging

Every Quick Action run generates an itemized execution breakdown in the Activity Log (execution_history), showing exact per-issue statuses ([SUCCESS] PROJ-1, [FAILED] PROJ-5: Workflow condition failed).

3. One-Click Resumption Tokens

If a bulk operation is interrupted or times out:

1. ScriptFabric sets the job status to PARTIAL_FAILURE or TIMED_OUT.
2. A Partial Failure Summary Banner appears in the Quick Actions UI and Activity Log showing exact counts (e.g. Succeeded: 699 | Failed: 1 | Remaining: 1,300).
3. Clicking "↻ Resume Remaining" passes the stored resumeCheckpointToken to the engine.
4. Execution resumes starting at item 701 without re-processing items 1 through 699 or producing duplicate transitions.

---

Execution Budgets & Timeouts

Feature	Limit	Notes
Maximum JQL Batch	Unlimited	Processed asynchronously via Forge queue
Async Queue Budget	14 minutes (840s)	Large jobs process up to 14 mins per queue cycle
Checkpoint Interval	Every 15–20 items	Saved continuously to prevent data loss
Resume Token Validity	Persistent	Resumable anytime from the Activity Log

---

Best Practices for Running Bulk Quick Actions

• Validate JQL First: Always run your JQL in Jira Search before starting a bulk operation to confirm the affected issue count.
• Review Itemized Errors: If a job finishes with PARTIAL_FAILURE, inspect the itemized error table to fix permission or workflow rule issues before clicking Resume Remaining.
• Use Activity Log: Check Execution History → Itemized Results for full audit trails of historical bulk operations.