Automation: Set default Organizations and Request Participants in Service requests
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Set default Organizations and Request Participants in Service Requests.
These rules add a default Organization or Request Participant when an issue is created, without clearing any existing Organizations or Request Participants already on the request. Use them when every request should always reach a baseline set of stakeholders.
Diagnosis
Sometimes, a customer comes with a request that all their requests need to be shared with a default organization or set of request participants (without clearing the existing organization/Request Participants from the support request). These requirements can be achieved using Jira Automation.
Solution
Automation rule to add Default Organization:
Trigger: Issue Created
Action: Re-Fetch Issue Data
Action: Edit Issue Fields
In the Edit Issue Fields action, the Organizations field offers a Copy from Issue option — this preserves the values already on the current issue and appends your default on top. Spell this out so readers understand it prevents overwriting:
Organizations: choose Copy from Issue, then add your default organization (e.g. Test3).
Automation rule to add Default Request Participant:
Trigger: Issue Created
Action: Re-Fetch Issue Data
Action: Edit Issue Fields
In the Edit Issue Fields action, the Request Participants field offers a Copy from Issue option — this preserves the values already on the current issue and appends your default on top. Spell this out so readers understand it prevents overwriting:
Request Participants: choose Copy from Issue, then add your default participant users.
Here are some reference documents for similar operations:
Verify if it worked
Create a test request that already has one Organization/Participant set, then confirm the default is added alongside it (not replacing it).
Was this helpful?