How to add a new team member to open Jira Service Management requests as a participant

By Kayabyte · Updated 18 November 2026

Short answer: Jira Service Management doesn’t add someone to requests that already exist when they join a Jira group, because Request participants holds individual people and nothing follows the group. The native routes are adding the person to each open request by hand, or running a script or Automation rule that lists the group’s members and sets Request participants again. Group Participants is a Marketplace app I make: with its hourly check switched on, people who join a group are added to the matching open requests, and Sync open requests now brings existing requests in line on demand.

Disclosure: I make Group Participants. The native options come first.

A new finance analyst joins the team that follows every invoice question. They are in the Jira group, but the 40 requests that are open today don’t list them, so they can’t see or answer those requests until somebody adds them. This guide covers what you can do without an app, where it stops, and what the app does and doesn’t do.

Native options

Where the native routes stop

Using Group Participants for joiners

How the app behaves, from its documentation:

Limits: it needs Jira Service Management Cloud, only active Atlassian accounts are added, portal-only customers can’t be in Jira groups so they can’t be added, and the hourly check is not instant. It runs on Atlassian Forge and makes no calls outside Atlassian.

It’s on the Atlassian Marketplace and free for up to 10 users. To compare it with other apps, see Group request participants apps for Jira Service Management compared.

Which one should you use?

Not a Jira admin? Send this to yours

Only an admin can install apps. Copy this note and send it to yours:

Could we try Group Participants? Add whole Jira groups as participants on JSM requests: rules per request type, an agent action and an optional hourly sync, off by default. It is on the Atlassian Marketplace and built on Atlassian Forge, and it makes no calls outside Atlassian. Free for up to 10 users. Listing: https://go.kayabyte.dev/atl/group-participants?s=site-ask-jsm-add-new-team-member-to-open-requests

FAQ

Does Jira add a new group member to existing requests? No. Request participants holds individual people, so existing requests keep the list they had.

Can I add someone to all open requests at once? Yes, with a script or an Automation rule that sets Request participants on the requests matching a JQL query, or with the app’s sync button. Each person added gets a “Participant added” email per request.

Will the app add a new joiner to requests that are already closed? No. It works on open requests, those whose status isn’t in the Done category.

What if the group is large or has many open requests? The hourly check holds back above 25 open requests per rule or 100 additions, and waits for you to run the sync button, which shows the numbers first.

Can it add customers who only use the portal? No. Jira doesn’t allow portal-only customers in Jira groups, so the app can only add people with an Atlassian account on your site.

Jira Service Management, Jira and Atlassian are trademarks of Atlassian. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.