Kayabyte

Group request participants apps for Jira Service Management compared

By Kayabyte · Updated 1 November 2026

Short answer: Jira Service Management can’t add a Jira group as request participants. Organizations share a request without making people participants, and Automation can add a fixed list of people. Four Marketplace apps fill the gap in different ways: Group Participants and Auto Participants add groups by rule on new requests, ParticipantFlow adds an Automation action that turns a group into participants, and Bulk Participants edits participants on many existing requests at once. Group Participants is the only one of these that also adds people who join a group to open requests. Its price for 11 to 100 users is higher than the other three; it is free for up to 10 users, where they charge a flat monthly fee.

Disclosure: Group Participants is the app I make. I’ve tried to describe every option fairly, including where another one is cheaper or does something mine doesn’t. Competitor facts come only from each app’s public Marketplace listing and its pricing data. Where a listing doesn’t mention something, the table says “not described” instead of guessing.

Checked on 1 Nov 2026; prices and features change, check each listing.

Comparison table

Organizations (built in) Automation, fixed list (built in) Group Participants (mine) ParticipantFlow for JSM Auto Participants for JSM Bulk Participants for JSM
Adds a group’s members on new requests No: shares the request, people don’t become participants A fixed list of people, not a group Yes, by rule Yes, inside an Automation rule you build Yes, by rule (Jira groups and organizations) No: works on requests you select
By request type No Yes, with a rule condition Yes Yes, with a rule condition Yes n/a
Agent adds a group in one click Agents can share with an organization Only with a manual rule Yes, from the actions menu Not described Not described (agents get a preview action) No (admin tool, JQL or issue keys)
Adds new group members to open requests Visibility follows membership No Yes, every hour and on demand No No (membership is read for each new request) No
Removes people who leave Visibility follows membership No Optional, off by default No, it only adds Not described By hand, with a preview
Runs on Atlassian badge n/a n/a Yes Yes Yes Yes
Price, 11 to 100 users (per user per month) Included Included, uses Automation runs USD 1.25 (USD 0.70 from 2 Nov 2026) USD 0.48 USD 0.50 USD 0.45
Up to 10 users Included Included Free USD 5 a month USD 5 a month USD 4.50 a month
Installs (Marketplace count) n/a n/a 1 0 1 1
Last update n/a n/a 30 Oct 2026 27 Oct 2026 30 Sep 2026 30 Aug 2026

All four apps are Forge apps for Jira Cloud, priced in user tiers. Marketplace apps for Jira are billed on the site’s Jira user count, not on the number of agents, so a desk with 5 agents on a 200-user site pays the 200-user price for any of them. None of the four has a review yet, and all are new, so installs don’t tell you much.

The built-in options

Organizations

Organizations group customers. When a request is shared with an organization, its members can see it in the portal, but they don’t become request participants: they get one “Organization added” email and later updates only if they turn notifications on for that request. Organizations are also separate from Jira groups. See JSM organizations vs request participants for the details.

Fits when: customers from one company should see each other’s requests.

Jira Automation with a fixed list

A rule triggered when a work item is created can set Request participants to named people, with a condition on the request type. It costs nothing extra, but the list lives in the rule. When someone joins or leaves the team, someone has to edit the rule, and requests that are already open don’t change. Each run counts towards the site’s monthly Automation usage. The steps are in Add a group as request participants.

Fits when: the list is short and rarely changes.

The apps

Group Participants for Jira Service Management

Group Participants is the app I make. Rules per service project pick request types and the Jira groups to add. When a matching request is created, everyone in those groups becomes a participant; the reporter and people already on the request are skipped. Agents can add any group from the work item’s actions menu. Every hour, people who join a group are added to the rule’s open requests, and removing people who leave is optional. It stores only its settings and member snapshots, makes no calls outside Atlassian, and doesn’t use your Automation runs.

What it doesn’t do: it works with Jira groups only, not organizations, and portal-only customers can’t be in Jira groups. Up to 1,000 open requests per rule are updated per sync. At 11 to 100 users it costs more per user than the three apps below, also after the lower price from 2 Nov 2026.

It’s on the Atlassian Marketplace.

Fits when: a team should follow certain request types and stay in step as people join, without maintaining lists.

ParticipantFlow for JSM

ParticipantFlow for JSM adds one action to Jira Automation: Add Request Participants. The source can be a Jira group (its active members, up to 500 per run), a list of emails, or a list of account IDs, with no API token or web request to build. It only adds: existing participants are kept and duplicates are skipped. Results come back as smart values for later steps. The listing says the group option needs the Administer Jira permission for the connected user.

Because it runs inside your own rules, you decide the trigger and conditions, and you can use emails and account IDs as well as groups. The rules count towards your Automation usage, and open requests don’t change when the group does.

Fits when: you already run Automation rules for requests and want a group step inside them. It is cheaper than Group Participants for 11 to 100 users.

Auto Participants for Jira Service Management

Auto Participants works much like Group Participants. Rules per service space and, optionally, request type add people when a request is created: the members of the organizations the request is shared with, of chosen organizations, or of a Jira group. Each rule has a cap, there is a daily limit and a group whose members are never added, admins can try rules on any request first, and agents get a preview action. It keeps a 30-day record of who was added and why anyone wasn’t.

It does two things Group Participants doesn’t: organization members as participants, and the caps and change record. Its listing doesn’t describe adding new group members to open requests or removing leavers.

Fits when: you want organization members as participants on new requests, or want caps against too many notifications. It is cheaper than Group Participants for 11 to 100 users.

Bulk Participants for JSM

Bulk Participants for JSM does a different job: an admin selects requests with JQL or issue keys, then adds, removes or replaces participants on all of them, with a required preview and an operation history. Its listing doesn’t mention groups or new requests.

Fits when: you need a one-off clean-up, such as removing someone who left from every open request. It is cheaper than Group Participants for 11 to 100 users.

How to choose

Whichever you pick, test it on one request type first. Jira Service Management only accepts participants who may raise requests in that service project, so group members without customer access are rejected by every option above.

FAQ

Can Jira Service Management add a group as request participants without an app? No. The Request participants field holds people, and Atlassian’s request for groups, JSDCLOUD-1268, hasn’t been built. Automation can add a fixed list of people.

Which app adds new group members to requests that are already open? Of the four, only Group Participants describes it: an hourly sync adds people who join a group to matching open requests. The other listings work on new requests or on requests you select.

Which apps are cheaper for 11 to 100 users? ParticipantFlow (USD 0.48), Auto Participants (USD 0.50) and Bulk Participants (USD 0.45 per user per month) are all cheaper than Group Participants (USD 1.25, or USD 0.70 from 2 Nov 2026). For up to 10 users, Group Participants is free and the others charge USD 4.50 to 5 a month.

Are these apps priced per agent? No. All four use user tiers, and Marketplace apps for Jira are billed on the site’s Jira user count.

Can any of them add organization members as participants? Auto Participants can, from the organizations a request is shared with or from chosen organizations. Group Participants works with Jira groups only.

Do these apps send data outside Atlassian? All four have the Runs on Atlassian badge on their listing, which Atlassian gives to Forge apps that run and store data on Atlassian’s infrastructure and send no data outside it.

Jira Service Management, Jira and Atlassian are trademarks of Atlassian. Other app names are the property of their owners. Kayabyte is an independent developer and is not affiliated with or endorsed by Atlassian.