Originally asked by Krzysztof Bartosiewicz on 20 October 2021 (original question)
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?
Kind regards
Chris
Comments:
Ariel Aguilar commented on 22 October 2021
Hi Chris,
You can do something like:
Outgoing:
replica.reporter = issue.reporter
replica.assignee = issue.assignee
Incoming:
issue.customFields."Assignee".value = replica.assignee?.displayName
issue.customFields."Reporter".value = replica.reporter?.username
Kind regards,
Ariel
Daniel Carvajal commented on 22 October 2021
Hi Krzysztof
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:
| 1 | issue.customFields.``"Your custom field name"``.value = replica.reporter?.email |
|---|
Hope this is helpful.
Cheers,
Daniel
Krzysztof Bartosiewicz commented on 24 October 2021
Hi - does it mean that it is not possible to use graphical matching once a new custom field is introduced?
Ariel Aguilar commented on 21 December 2021
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.
Kind regards,
Ariel