The Exalate team will be on holiday for the coming days - returning Jan 4
Enjoy & stay safe
Hello we are testing the plugin before buying. We have a case when we want to move information about assignee and reported to text custom fields on other side (to avoid the need of creating users). The problem is that after I added the customfields on JIRA1 when I try to change the mapping I got a blank page after publishing. On JIRA2 I cannot see the new field. I tried creating new account - the same. Is there any option to force synchronization of fields? Am I doing something wrong?
You can do something like:
replica.reporter = issue.reporter
replica.assignee = issue.assignee
issue.customFields."Assignee".value = replica.assignee?.displayName
issue.customFields."Reporter".value = replica.reporter?.username
The method to do this is best described here: https://docs.idalko.com/exalate/x/TwR1Aw
In case of the reporter it would be the same approach, just making sure
"replica.reporter = issue.reporter" Is being sent in the outgoing script and adjust the incoming script to:
replica.reporter = issue.reporter"
issue.customFields."Your custom field name".value = replica.reporter?.email
"Your custom field name"
.value = replica.reporter?.email
Hope this is helpful.
Hi - does it mean that it is not possible to use graphical matching once a new custom field is introduced?
Hi Krzysztof Bartosiewicz
If you encounter a limitation using a Visual Connection, you might need to add a script to make proper mapping as stated here: https://docs.idalko.com/exalate/x/ogXHAw
Then, for advanced mappings we recommend to start the connection using the script based connection.
© 2019 Exalate. All rights reserved.