Auto Participants documentation

Would native Jira Automation be enough?

Jira Automation can preserve existing request participants while appending fixed defaults. Atlassian also documents adding Jira-group members and all members of the organizations shared on a request using Automation and REST. If those patterns already meet your needs, you may not need an additional app.

Consider Auto Participants when you want to evaluate managing organization or Jira-group participant rules through an app interface instead of maintaining your own Automation and REST setup. This is a configuration choice, not an exclusive capability or a proven saving in Automation runs.

Compare the current Marketplace description and your installed version. Start with non-sensitive requests and verify the final participant set, including existing people and skipped candidates. A source review or an individual successful API response does not prove overlapping runs are safe.

Atlassian: default organizations and request participants

Atlassian: add group members as request participants

Atlassian: add all organization members as request participants

Review pricing and trial options

Use the official Marketplace Pricing tab for a quote for your site, including the applicable user tier, billing period, renewals and taxes.

Use Try it free on the Marketplace listing to review the available trial flow. Atlassian determines availability and terms for your site; review them before starting a trial or installing. This page does not promise a fixed price or trial duration.

Atlassian Marketplace pricing for your site

Install and check your first rule

• Open the Atlassian Marketplace listing linked from the product page and install Auto Participants on your Jira Service Management Cloud site as an administrator.
• Open Auto Participants from Jira settings under Apps. Create a rule limited to a test service space and a small organization or group.
• Use Try the rules on a request to check the counts and skipped reasons before enabling the rule more widely.
• Create a test request in that space, confirm its participants and the Activity counts, and check Jira Service Management notification settings. The app does not send notifications itself.

Requirements

• Jira Service Management Cloud, and the ability to install an application on the site.
• A Jira administrator to create the rules. Administrators are the only people who can create, change, enable or delete them.

Creating a rule

In Jira settings, under Apps, the Auto Participants page lists every rule. A rule names the service spaces it applies to, optionally the request types, and who to add: the members of the organizations the request is shared with, the members of specific organizations, or the members of a Jira group.

A rule can also name a group whose members are never added, the most people it may add to one request (1 to 100, 25 by default), and whether it should also run when a request’s organizations change.

What happens when a request is created

• Every enabled rule that matches the request’s service space and request type runs.
• The people it finds are added as request participants, up to the rule’s limit. The reporter, existing participants and members of the excluded group are left out.
• Jira Service Management then treats them like any other participant and sends its usual notifications.
• The result is recorded on the Activity tab for 30 days.

Checking a rule

• On the Activity tab, “Try the rules on a request” shows how many people each enabled rule would add and the reasons for skipping others. Nothing is changed; participant identities are not shown in this preview.
• On a request, “Add participants from rules” shows the same counts to an agent with permission to add participants. It adds the people only when that agent confirms, using that agent’s Jira permissions.

Limits you should know

• At most 100 people are added to one request, whatever the rules say.
• An organization, group or participant list is read in full up to 5,000 accounts. If a list exceeds that safety limit, the rule adds nobody and reports the limit instead of using a partial list.
• A site-wide limit of 5,000 additions a day stops runaway rules.
• Customers who have not confirmed their email address are asked to confirm it before Jira Service Management sends them request notifications.