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
- By hand, per request. An agent opens the request and adds the person under People → Request participants. Fine for a handful of requests, tedious for forty.
- A script that re-sets the participants. The free atlassian-admin-scripts repository has a
jsm-group-participantsscript that adds a group’s current members as participants on one request or on the requests matching a JQL query. It uses the public REST API and runs once, so you run it again when the next person joins. - An Automation rule with web requests. Atlassian documents a rule that looks up a group’s members and sets Request participants (How to add group members as request participants). It adds the members present when the rule runs. The step by step is in How can I add a whole group as request participants in JSM?.
- Rule builder. The free JSM request participants rule builder gives you the JQL for the open requests and the curl calls, in your browser.
Where the native routes stop
- Nothing follows the group. Each route adds the members at the moment it runs. The next joiner means another run.
- Everyone gets an email, again. Jira Service Management sends the “Participant added” notification to each person added to a request. Re-running over open requests can email people who were already on them or add many emails at once, so read why bulk adds flood inboxes before you start.
- Not everyone can be added. Jira Service Management only accepts participants who can access the service project as customers. Others are rejected.
Using Group Participants for joiners
How the app behaves, from its documentation:
- New requests: a rule per request type adds everyone in the chosen groups. A new joiner is covered from then on.
- Open requests: switch on Keep open requests in step with group membership (it’s off by default). Each hour the app compares each group’s current members with the ones it saw last time and adds the new members to the rule’s open requests, meaning requests whose status isn’t in the Done category.
- Limits that protect inboxes: at most 25 open requests per rule and 100 person-to-request additions per hourly check. Above either limit the app adds nobody and shows a warning on the settings page, because Jira would email each person once per request. They are added when you run the sync button, or at a later check under the limits.
- Sync open requests now: adds every current member, not only new ones, to up to 1,000 open requests per rule. It shows how many people and requests are involved and the most emails Jira can send, then waits for your confirmation.
- Leavers: removal is off by default. If you switch it on, the app removes only people it added itself while that setting was on.
- Results: the app reports how many people were added, skipped or could not be added.
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?
- One joiner and a few open requests: add them by hand.
- A recurring chore for one team: the documented Automation rule or the script, run when people join.
- Several teams, new joiners often, and you want open requests to follow the group: an app.
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.
More guides
- Atlassian Connect end of support: what Jira and Confluence admins should check before 31 January 2027
- How to delete old page versions in Confluence Cloud
- Apps to make a Confluence group watch a space or page, compared
- How to make a Confluence group watch a space or page
- Can you limit how many page versions Confluence Cloud keeps?
- Onboarding in Confluence: make new hires watch the right spaces automatically
- Confluence storage almost full? What counts and how to free it
- Apps to delete old Confluence page versions, compared
- Confluence watching but no email? 5 things to check
- How to track billable and non-billable hours in Jira
- How to calculate budget burn rate and run-out date in Jira
- Jira business days apps compared: JQL, Automation and holidays
- How to count business days between two dates in Jira
- How to see what a Jira epic costs from worklogs
- How to set a Jira due date N business days ahead (skip weekends and holidays)
- How to export Jira worklogs to Excel or CSV
- How do I make a Jira field read-only after approval?
- How to handle hourly rate changes in Jira cost reports without changing past costs
- How to track project cost in Jira without showing everyone hourly rates
- Can Jira stop one person from having too many work items?
- How do I stop people editing a Jira work item after it is closed or Done?
- Jira project cost and budget apps compared: Tempo Financial Manager alternatives
- How to track project cost and budgets in Jira from worklogs
- How to see project cost from Tempo worklogs in Jira
- How to set a WIP limit per person in Jira
- How to see workload per assignee in Jira
- How to invoice Jira worklogs in Fiken
- How to invoice Jira worklogs in Fortnox
- How to invoice Jira worklogs in PowerOffice Go
- How to invoice Jira worklogs in Tripletex
- JQL with business days: find Jira work due within N working days
- JSM agent can’t find a customer in Request participants: what to check
- Add or remove request participants with Jira Automation
- CC a whole team on every Jira Service Management request
- Why can’t a customer see a JSM request shared with their group or organization?
- How to calculate on-call pay from Jira Service Management schedules
- JSM organizations vs request participants: which to use
- Stop agents or the reporter ending up as request participants
- How to add public holidays to a JSM SLA calendar
- Kanban WIP limit per person in Jira: beyond column limits
- Kayabyte apps for Jira and Confluence: what each one does
- What happens to your worklogs when you leave Tempo Timesheets (Jira Cloud)
- Opsgenie to Jira Service Management: on-call pay reports
- Purge Versions for Confluence after moving to Cloud: what replaces it