JIRA SERVER JIRA CLOUD
Components field is one of the standard fields of an issue. You can synchronize them as any other issue field.
This article helps to synchronize issue components and create a new component if it does not exist on the destination side.
Component issue field reference.
Send issue components to the destination side:
Exalate uses CreateComponent nodeHelper to create a new component and add it to the Components field.
Add the code below into the Incoming sync to create components on your side. To update components use the same code in the Incoming sync(change processor).
If you sync components with Jira Cloud there're several ways to create components, depending on the information you know about the remote side.
map the remote component lead email to the local component lead email
set default component lead if the remote component lead email is not found
Do not create a new component but try to look for the same one by name
If you sync components between Jira Server instances and the usernames match, add the code below into the Incoming sync
If you want to sync the components with Jira Server, you need to map the remote component lead email to the local component lead email.
If you sync between Jira Cloud instances use the code below
The user with the specified accountId must be a user on your instance.
How to assign synced issue to an existing component?
The receiving side is looking for an existing component and assigns the issue to the lead of this component.
Back to General articles