Confluence has been updated to ver 6.15.9. In case of any troubles, please contact infra team.
The problem here is with that line you added you are only sending the custom field information, now you need to add logic in the Incoming Sync (destination side - Jira Cloud) to actually set that field into a custom field on that destination issue.
You have this:
Outgoing sync (source side - Jira Server):
replica.customFields."Partner Name" = issue.customFields."Partner Name”
You are missing this:
Incoming sync (destination side - Jira Cloud):
issue.customFields."Partner Name".value = replica.customFields."Partner Name"?.value
This is assuming that the field is also called "Partner Name" on the Cloud side and that the field if of type Text
I tried this and update the ticket. But is not syncing the field. Probably some issue with the field name. So how can i test this but the field ID.
For example this is the ID of the field on the cloud: 10033 and this is the field's ID on the server: 10403.
How can i apply it here:
Outgoing (Jira Server):
replica.customFields."Partner Name" = issue.customFields."10403"
Incoming (Jira Cloud):
issue.customFields."10033".value = replica.customFields."Partner Name"?.value
Let me know!
Nice! It's working! Thanks André!
One question about this, There are some old fields we want to sync since they weren't created after the first synchronisation. How can i sync this fields?
You can just add the logic to sync those fields to the sync rules of the connection and then if you update the tickets (change the summary, add a comment, for example), this will trigger a new sync and will sync those fields over.
© 2019 Exalate. All rights reserved.