How to Bulk Update Request Participants in Jira Service Management

Jira Service Management administrators often need to update Request Participants across multiple requests. When teams manage large service desks, manually opening each request can become time-consuming and inconsistent.

Bulk Participants for JSM provides a safer way to manage Request Participants across multiple Jira Service Management requests using a preview-first workflow.

The challenge of managing Request Participants at scale

Request Participants are important for keeping the right people informed during Jira Service Management workflows. However, updating participants across many requests can become difficult when handled one ticket at a time.

Common situations include:

• Adding a team member to many existing requests
• Removing someone who is no longer responsible for requests
• Replacing participant lists during team changes
• Updating requests after organizational changes

Common approaches and their limitations

Manual request editing

Editing requests individually works for small changes, but becomes slow and difficult to audit when dozens or hundreds of requests are involved.

Temporary scripts

Jira administrators sometimes use scripts or API calls for bulk changes. While powerful, scripts require maintenance, testing, and careful handling of permissions.

Automation rules

Jira automation can solve many workflow problems, but it may not be the best fit for a one-time administrative update of existing requests.

A safer bulk update workflow

Bulk Participants for JSM is designed around a simple administrator workflow:

1. Select requests
   Find Jira Service Management requests using JQL or pasted issue keys.
2. Review the request set
   Confirm which requests will be affected before making changes.
3. Choose an action
   Add, remove, or replace Request Participants.
4. Preview before applying
   Review the expected changes before anything is modified.
5. Review results
   Check operation history and outcomes after completion.

Who is this for?

Bulk Participants for JSM is designed for:

• Jira Service Management administrators
• Service desk administrators
• IT support teams managing many requests
• Teams responsible for Jira workflow maintenance

Why use a preview-first approach?

Administrative changes should be predictable. Previewing changes before applying them helps administrators understand what will happen before modifying multiple Jira Service Management requests.

Try Bulk Participants for JSM

Bulk Participants for JSM is available through Atlassian Marketplace.

View Bulk Participants for JSM on Atlassian Marketplace

Learn more

View the full Bulk Participants for JSM documentation or visit the support page for assistance.