This article shows how to move issues automatically with the External scripts library.
This script handles the situation when you move issues from one workflow to another workflow on the source system.
|Source side||Destination side|
1. Upload the file with the external script
You need to upload the Move.groovy file into the scripts directory
External scripts library location
Jira Server: $JIRA_HOME/scripts
2. Call the script from the Sync Rules
Once all external .groovy files have been uploaded to the proper directory, you need to call the script from the Sync Rules.
Every .groovy file includes comments with a detailed explanation on how to use it. Please check the file comments.
Add the snippet below to the new line in the end of the data filter
Add the snippet below to the new line in the end of the change processor
Move issues automatically according to the specified mapping
The method helps to move issues automatically in case the source issue has been moved to another project or the issue type has been changed on the source side.
Move issue with identical workflows for all issue types
If the workflows are identical for all issue types, you don't need to specify the status mapping. But you still need to specify project and issue type mappings if the projects and issue types are different.
Move issue with different workflows for all issue types
moveStatusMapping - defines, the status of the issue moved to another workflow.
If an issue which is under sync is moved from LocalWorkFlow1 to LocalWorkFlow2 and the current status is OPEN, set the status TO DO.
Example: [...,"LocalWorkFlow1":[...,"LocalWorkFlow2":[...,"OPEN":"TO DO",...],...],...]
Incoming sync for existing issues(change processor)