How it works

On a new request. When a request is created, the app checks the project’s rules. If the request type matches, it reads the active members of the rule’s groups and adds them as participants. The reporter and anyone already on the request are skipped.

On the hourly check. For each rule, the app compares the group’s current members with the members it saw last time. New members are added to the rule’s open requests (requests whose status is not in the Done category). With removal switched on, people who left the group are removed from those requests.

On “Sync open requests now”. The same as the hourly check, except every current member is added, not only new ones. Use it after creating a rule or when you are unsure everything is in line.

Limits. - Up to 1,000 open requests per rule per sync. If a rule matches more, the status line says so and the rest are not updated; contact support if you need a higher limit. - Only active Atlassian accounts are added. App and bot accounts are skipped. - Jira Service Management decides who can be a participant. See the FAQ for people who cannot be added.

What the app stores. Its settings, the result of the last sync, and a snapshot of each rule’s group members (Atlassian account IDs) so it can see who joined or left. Everything stays in Atlassian’s Forge storage; the app makes no calls outside Atlassian.