A preset is a saved bulk operation — operation type plus all its parameters — that you can re-run with one click. Presets are perfect for repeat workflows like daily triage, sprint cleanup, or release tagging.

Creating a preset

1. Go to Apps → BulkOps Presets in the top nav. The first time you open it, no presets are saved yet — the Create New Preset form is shown right below.

BulkOps Presets page with empty state

1. Enter a Preset Name (e.g. Triage: label and assign to lead).
2. Pick an Operation from the dropdown.

Operation dropdown listing all available operations

1. Fill in the operation's fields (e.g. labels, assignee, target project).

Filled-in preset form

1. Click Save Preset. The new preset appears at the top of the Saved Presets list.

Saved preset listed at the top of the page

The preset is saved at the site level — anyone with the app installed can see and use it.

Running a preset

From the issue navigator's BulkOps action, choose Run Preset (Paid) as the operation, pick the preset from the dropdown, and click Execute on N issues. The preset runs against whatever issues are currently selected (or matched by JQL).

Running a saved preset from the issue navigator

Editing and deleting

On the BulkOps Presets page, every saved preset has Edit and Delete buttons. Editing replaces the preset's configuration; deleting removes it permanently (it does not affect the audit log of past runs).

Tips

• Use descriptive names — the dropdown shows just the name when running.
• Presets are great for operations that take several fields to fill in (e.g. Move needs a target project and issue type).