Bulk Approvals for JSM

Availability

Bulk Approvals for JSM is currently in release preparation. Installation through Atlassian Marketplace will be documented here when the production listing is available.

Project configuration

A Jira Service Management project administrator configures Bulk Approvals from the project's Bulk Approvals settings. Configuration applies only to that project.

1. Select the supported request types that should appear in the approval view.
2. For each request type, choose up to three eligible portal-visible fields to provide decision context.
3. Choose whether Approve, Decline, or both actions are available, then save the configuration.

If a configured field later becomes unavailable or unsupported, the app warns the administrator rather than inventing or exposing a replacement value.

For approvers

The app shows native approvals currently awaiting the signed-in portal approver. Jira remains responsible for deciding which requests that person can see and approve.

1. Review the request key, summary, requester, request type, submitted date and any configured decision context.
2. Search by request key, summary or requester when needed.
3. Select individual requests, or Select all visible when 25 or fewer eligible results are shown.
4. Choose Approve or Decline and review the exact frozen confirmation before submitting.
5. Review the per-request results after the app refreshes against Jira.

Understanding results

Each selected approval is handled independently. A stale, inaccessible or failed request does not undo successful decisions on other requests.

The results distinguish confirmed decisions from stale, failed, unattempted or unconfirmed outcomes. Uncertain writes are not blindly retried. The refreshed Jira state remains the source of truth.

In multi-approver workflows, your native decision does not necessarily mean the overall request has reached its final approved or declined workflow state.

Important limits

• Maximum batch size: 25 approvals.
• Decision-context fields: up to three eligible fields per supported request type.
• The app does not replace Jira permissions, approval rules, workflow transitions or audit history.
• The app does not require a customer personal access token or API token.

Licensing

When a production Marketplace entitlement is inactive or cannot be verified, the app fails safe and does not expose approval actions. For licensing help, contact support@peztechsoftware.co.uk.

Getting help

See the Support Policy before sending diagnostics. Do not email passwords, API tokens, Jira request or approval content, sensitive custom-field values or unnecessary personal information.