Atlassian · Jira Service Management

Auto Participants

Adds the right people to Jira Service Management requests by organization or group.

Per-site price shown on the Atlassian listing

See price and install on Atlassian

Listed on the Atlassian Marketplace.

Billing and any trial run through Atlassian.

Works with Jira Service Management
Marketplace Atlassian Marketplace

Auto Participants at a glance: the problem, what it does, the result.
Real product screen with demo or test data.

Live

Available on Atlassian Marketplace

Auto Participants has a public Atlassian Marketplace listing for Jira Service Management Cloud. Open the listing, choose Pricing for your site's quote, or use Try it free to review the trial flow and terms shown by Atlassian before starting. Check the currently supported features and installation requirements.

View Auto Participants on the Atlassian Marketplace

Listed onAtlassian Marketplace

What it does

Auto Participants is available on Atlassian Marketplace for Jira Service Management Cloud. Its rule interface is designed for organization and Jira-group participant rules. Compare the current Marketplace feature list, permissions and pricing with your service desk before installing. Native Jira Automation can also add default participants, Jira-group members or request-organization members through Automation and REST; an additional app may not be necessary.

Capabilities

Marketplace pricing

Atlassian handles billing. Use the pricing calculator on the app’s Marketplace listing to see the price for your site, the user tier that applies, monthly or annual billing, renewals and taxes before installing.

Organization members, kept informed

Rules can use members of the organizations shared on a request as participant candidates. Whether a person receives notifications depends on Jira Service Management permissions, notification settings and account status; the app does not send email itself.

Groups and fixed organizations too

The rule interface supports selected organizations or a Jira group as candidate sources for named service spaces and optional request types. Organization- and group-based participant addition is also possible with native Jira Automation and REST; compare which setup you prefer to manage.

Guardrails against notification spam

The rule engine checks existing participants, the reporter, repeated candidates and an optional excluded group before selecting additions. Configured caps and a daily budget limit additions. Check the installed version and a small request before adopting a rule widely; these controls are not a guarantee of race-safe overlapping runs.

See before it happens

Administrators can try the rules on an existing request and see how many people each rule would add and why others would be skipped, without changing it. Agents with permission to add participants can review the same counts before confirming.

A record of every change

For 30 days the application keeps the request key, time, rule names and counts of people added, refused or skipped, with the reasons. Activity records do not keep participant account ids, names or email addresses and are deleted automatically.

Nothing leaves your Atlassian site

The application runs entirely on Atlassian Forge: Atlassian-hosted compute and storage, no external network calls, no analytics and no email of its own. Jira Service Management sends its normal notifications. Atesen Software operates no server for it and cannot see your data.

Questions

Where does Auto Participants run?

Auto Participants is an Atlassian Forge application. Its interface and its functions run on infrastructure operated by Atlassian, and it stores data only in Atlassian-hosted storage provisioned for your own installation. Atesen Software operates no server and no database for it.

The full Auto Participants privacy page

What does Auto Participants connect to?

Only your own Jira site. The application requests no external network egress. It uses no analytics or external service and sends no email of its own.