JSM request participants rule builder

Type a service project key, the request types and the Jira groups, and get the JQL that finds the matching open requests, a curl sequence that adds every group member as a request participant, the matching command for a free script, and a note on what Jira Automation can and can't do. It runs in your browser: nothing you type is sent anywhere.

How the REST calls work

1. GET /rest/api/3/groups/picker finds the group's ID from its name.
2. GET /rest/api/3/group/member lists the group's active members, 50 per page, with isLast telling you when to stop. It needs the Browse users and groups or Administer Jira global permission.
3. POST /rest/api/3/search/jql returns the keys of the matching requests, up to 100 per call (use nextPageToken for more).
4. POST /rest/servicedeskapi/request/{key}/participant adds people with {"accountIds": [...]}. You need permission to manage participants on each request, and the people need access to the service project, or that batch is rejected.

Use an API token as the password with your Atlassian email. Run it on one request first: the sequence adds people to every request the JQL matches.

What Jira Automation can and can't do here

• Can: when a request is created, a rule with a request type condition can set Request participants to a fixed list of people.
• Can't, simply: turn a Jira group into its current members. The list lives in the rule, and someone has to edit it when people join or leave.
• Can't: change requests that are already open when the list changes, unless you build a second rule that goes through them. Every rule run also counts towards your plan's monthly Automation usage.
• Can't: remove people who left the group.

The script and the curl sequence run once, so run them again when people join. For the longer comparison of organizations, Automation and apps, see Add a group as request participants in Jira Service Management.

Prefer it automatic?

Group Participants keeps groups in sync: rules per request type add everyone in the chosen groups to new requests, and an hourly sync adds people who join a group to matching open requests. It is free for up to 10 users.

FAQ

Can I add a Jira group as a request participant? No. The Request participants field holds individual people, so a group has to be turned into its members first. That is what the calls above do.

Does the JQL work for every service project? It limits the search to the project you typed and matches request types by name with the "Request Type" field. If two request types in a project share a name, pick the value from the JQL autocomplete instead, which gives a form like "sd/system-access".

Is anything uploaded when I use this page? No. The page builds the text locally in your browser. It does not call Jira, and your project, group and site names stay on your device.

Will the commands change anything before I run them? No. Nothing is changed until you run the commands yourself. The script has a --dry-run option that lists what it would add.

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