Approved Bulk Actions documentation

Availability and installation

The app is awaiting Atlassian Marketplace review and is not available for public installation yet. After it is approved and listed, open its Atlassian Marketplace listing, choose Get it now, select your Jira Cloud site and review the permissions Atlassian presents before confirming installation.

Requirements

• Jira Service Management Cloud, and the ability to install an application on the site.
• A Jira administrator to create the saved actions. Administrators are the only people who can create, change, enable or disable them.
• Agents who are members of the groups or project roles an action names.

What an administrator sets up

In Jira settings, under Apps, the Approved Bulk Actions page lists every saved action. Creating one asks for its name, the service spaces it may touch, an optional JQL filter that selects the requests, the maximum number of requests a single run may change, and the groups or project roles allowed to run it.

The changes an action can apply are: assignee, priority, labels added or removed, components, single and multiple choice fields, a relative shift of a date field, request participants, and a comment as either an internal note or a reply to the customer. The options offered come from the service space itself, so only fields that space actually has are shown.

How an agent runs one

• Open the service space, then Queues, then Bulk actions.
• Choose an action. Only actions approved for you, in this space, are listed.
• Optionally add your own JQL to narrow it further. It is added to the administrator’s filter and can only reduce the set of requests.
• Preview reports how many requests match. What can I change? reports how many of those you may edit, and names those that would be skipped.
• Dry run shows the current and proposed values for a sample of real requests. Nothing is written.
• Run asks for confirmation, then works through the requests in batches, showing progress. You can stop it between batches.

Limits you should know

• A run changes at most the number of requests the administrator set for that action, and never more than 1,000.
• One run at a time per person. Different agents can run actions at the same time.
• If Jira asks the application to slow down, the run waits for the period Jira asks for and then continues.
• Finished run records become eligible for cleanup after 30 days. Cleanup runs when another run starts, so records may remain longer if no later run starts.
• The first time an agent opens the page, Atlassian asks them to allow the application to act on their behalf. That consent is what lets the application check their permissions.

Troubleshooting

• No actions listed: you are not in a group or project role the administrator approved for this space, or every action for this space is disabled.
• Jira cannot read this JQL: the filter is not valid Jira Query Language. The application checks it with Jira before running anything.
• Requests skipped: Jira reports you cannot edit them. Ask an administrator about your permissions in that space.
• A request failed: the reason Jira gave is recorded against that request in the run, and in the CSV export.

Permissions and data

• The submitted Forge manifest declares read:jira-work, read:permission:jira, read:jira-user, write:jira-work, storage:app and report:personal-data. Jira uses these scopes for request search and field reads, permission checks, approved writes, app storage and weekly privacy reporting.
• The app runs on Atlassian Forge and makes no external network calls. Saved action definitions and run metadata are held in Atlassian-hosted storage for your installation; request contents are not retained as run data.
• Run records include the selected action and changes, search, acting Atlassian account ID, counts and each request outcome. A saved action or run can contain administrator-entered comment text or configured participant account IDs; a Jira error message saved with an outcome may include a field value. See the privacy page for the full data inventory and retention details.

Demo video plan (script only)

A 78-second scene-by-scene demo script is available. No recording is included or claimed.

Open the Approved Bulk Actions demo script

Publisher and product names

Approved Bulk Actions is published by Atesen Software, an independent third-party Marketplace vendor. Jira and Jira Service Management are Atlassian product names; this product is not made, sponsored or endorsed by Atlassian.