JIRA SERVERJIRA CLOUD
There might be multiple use cases in issue types synchronization.
The Exalate app allows handling any possible combination of the issue type mapping.
To send the issue type, add this script below to the Outgoing sync
There are different approaches to how you can set the issue type on the receiving side, depending on your specific use case.
To add the issue type on a synced issue you should add the script to the Incoming sync.
Below you can find some of the most common cases:
Set the issue type name from the source issue, if not found set a default one
Set the issue type according to the mapping, specified with the help of Groovy scripts
- You can also keep the issue type when syncing in case the issue types are identical on both sides.
Supporting issue type changes
There are 2 ways to change the issue type in Jira: edit issue type field or change the type using move issue operation.
An issue type change is a move operation within Jira context. It requires some low-level JIRA data manipulation.
This will only work if workflow scheme of the target issue type is the same as the source issue type.
You can automatically trigger issue type change by move operation with the help of Exalate and Sync Rules. We've developed special external script for this - Move.groovy.
Check how to move issues automatically depending on a specific condition.
If you want to sync issue type with different workflows, please contact us at email@example.com for more details.
Back to advanced configuration