Who it is for
JSM portal approvers
Authenticated approvers who regularly have several native Jira Service Management requests waiting for their decision.
Bulk Approvals for JSM
Jira Service Management app
Bulk approvals without replacing JSM approvals.
Coming soonPreparing for Atlassian Marketplace
Who it is for
Authenticated approvers who regularly have several native Jira Service Management requests waiting for their decision.
The problem
Common approval decisions can require opening and working through requests individually even when the same approver is responsible for several.
The outcome
Review useful context, select up to 25 approvals, confirm the exact batch and see a result for each request while Jira remains authoritative.
Jira Service Management portal customers may have several native requests waiting for their approval, while the normal customer experience requires them to work through those requests individually.
Bulk Approvals gives an authenticated JSM portal approver one focused place to review and action the approvals already awaiting their decision.
Review and decide multiple pending approvals together.
See enough request information to make common decisions without opening every request.
Existing Jira permissions, workflows, approval rules and audit history remain authoritative.
See the request key, summary, requester, request type and submitted date for native approvals awaiting your decision.
Search by request key, summary or requester, then select individual approvals or all visible matches when 25 or fewer are shown.
Select up to 25 approvals, review the exact confirmation, then submit an Approve or Decline decision.
See confirmed successes, stale or failed items, unattempted items, and outcomes that could not be confirmed. Each is handled safely before the view reconciles against Jira's current state.
A project administrator can configure up to three suitable fields per request type so approvers can see useful decision information in the focused view. Examples might include Cost, Supplier or Department; these are illustrations rather than guaranteed built-in fields.
The native Jira request remains one click away whenever an approver needs more detail.
Bulk Approvals improves the approval experience without replacing Jira Service Management's native approval engine.
Jira remains authoritative for request visibility, approval authorisation, approval state, workflow behaviour, final workflow transitions, native audit history and attribution to the signed-in approver.
In a multi-approver workflow, the app records the current user's native approval decision. That decision does not necessarily move the request to a final workflow-approved state.
See it in action
A 34-second recording of the real app, using fictional demo requests. Review context, select requests and confirm a native Jira approval batch.
Reviewing Jira requests one at a time can be repetitive.
Bulk Approvals brings pending approvals together, with useful decision context.
Search the list, select requests, then approve or decline them together.
Before anything changes, review exactly what you're about to submit.
Bulk Approvals for Jira Service Management. Less repetitive work, using Jira's native approval process.
The recording shows three requests selected, a confirmation before submission, then processing and reconciled results after Jira refreshes. A native approval decision does not necessarily complete every workflow.
Screenshots show separate synthetic examples, not additional steps from the recorded batch. Select an image to inspect its original size. The app is preparing for Atlassian Marketplace and is not publicly available yet.
PezTech Software does not operate an external backend or database containing your Jira Service Management request or approval data. Request and approval information is processed within Atlassian's platform and is not copied to PezTech Software infrastructure.
Built on Atlassian Forge, with native approval actions remaining in Jira.
App configuration metadata uses Atlassian-hosted Forge storage. Request, approval, context, search, selection and result state is transient.
No PezTech-hosted Jira request or approval database, and no external PezTech analytics or telemetry receiving Jira request data.
Uses the signed-in Jira user and does not require a customer personal access token or API token.
The app does process customer-visible Jira and JSM information to provide its functionality. The distinction is that this information is not copied into a separate PezTech-operated Jira-data backend.
Simple Atlassian Marketplace pricing is planned, including a free 1–10 user tier. Paid tiers above 10 users will follow a low-cost utility model. Full pricing will be published when the app launches.
This is the current commercial direction and is not yet an available Marketplace offer.
The app is in release preparation and has not launched on Atlassian Marketplace. Installation, trial and final pricing links will be added only when they are real.
For help with Bulk Approvals for JSM, email support@peztechsoftware.co.uk. Initial responses are targeted within two business days.