Atlassian · Jira Service Management
Approved Bulk Actions
Let Jira agents run the bulk changes an admin approved, without global bulk permission.
Per-site price shown on the Atlassian listing
Install from Atlassian Marketplace
Listed on the Atlassian Marketplace since 29 October 2026.
Billing and any trial run through Atlassian.
- Works with Jira Service Management
- Marketplace Atlassian Marketplace
Live
Available on Atlassian Marketplace
Approved Bulk Actions has a public Atlassian Marketplace listing for Jira Service Management Cloud. Open the listing to see the price for your site, start the free trial Atlassian offers, and check the installation requirements.
Install from Atlassian Marketplace
Listed onAtlassian Marketplace
What it does
Approved Bulk Actions is a Jira Service Management application built on Atlassian Forge. A Jira administrator saves a bulk change once — which service spaces it covers, which requests it matches, what it changes and who may run it — and agents run it from their own queue with a preview, a dry run and an audit. Every run stays inside the Jira permissions of the person running it.
Capabilities
Bulk changes without the global permission
Jira’s Bulk change permission is global: an agent who holds it can edit issues in every project on the site. Approved Bulk Actions replaces that with a named change an administrator approves for specific service spaces, specific matching requests and specific groups or project roles. An agent runs that change and nothing else.
Never beyond the agent’s own rights
The application performs the writes, but before any request is changed it asks Jira which of the matching requests the person running it may browse and edit. Requests Jira does not grant are skipped and named in the result. The agent’s own filter is added to the administrator’s filter, so it can only narrow the set of requests, never widen it or reach another space.
Preview and dry run before anything is written
A preview reports how many requests match, using Jira’s own count, and refuses to start a run over the limit the administrator set. A dry run shows the current value and the proposed value for a sample of real requests. Neither writes anything.
Runs in the background, with a stop button
A run is processed in batches on Atlassian’s queue, so it does not depend on a browser tab staying open. Progress updates while it works, and a run can be stopped between batches. The list of requests is frozen when the run starts, so the set cannot drift while it is running.
An audit of every request touched
Each run records who ran it, when, the search it used and the outcome of every request, including the reason for anything that failed. Agents see their own runs; administrators see all runs and can export any of them as CSV.
Nothing leaves your Atlassian site
The application runs entirely on Atlassian Forge: Atlassian-hosted compute, Atlassian-hosted storage, no external network calls, no analytics and no logging of request data. Atesen Software operates no server for it and cannot see your data.
Questions
Where does Approved Bulk Actions run?
Our application-specific security policy describes access controls, vulnerability reporting and incident handling.
What does Approved Bulk Actions connect to?
The app uses Atlassian Forge services and your Jira site, including Atlassian's Privacy API to report stored account identifiers. Its manifest configures no external egress destination or remote backend. The app has no external analytics integration.
How do I get help with Approved Bulk Actions?
Support for Approved Bulk Actions is provided by email in English and Turkish.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- It is listed on the Atlassian Marketplace. There is no public installation count, customer list or review history to report yet.
- No duration is promised for a given number of requests. Throughput depends on Jira and on its rate limits.
- It holds no security certification and has not undergone a third-party audit.
- Scheduled or recurring runs are not part of the current feature set; a person starts every run.
- It is built for Jira Service Management. Other Jira products are not supported today.
Marketplace
Atlassian Marketplace: Available on the Atlassian Marketplace for Jira Service Management Cloud.
Install from Atlassian Marketplace
Listed onAtlassian Marketplace