Originally asked by Harold Oconitrillo on 06 December 2022 (original question)
Exalating between 2 Jira instances, trying to sync Start Date, which is treated as a custom field, with different customfield_IDs between the 2 instances.
Both Jira instances are using Scripting
Thanks.
Comments:
Harold Oconitrillo commented on 06 December 2022
Hi,
Is this configuration for JiraOnprem? If so, feel free to check the below documentation.
https://docs.exalate.com/docs/how-to-sync-date-and-datetime-custom-fields-in-jira-on-premise
Do not hesitate to contact us back for further questions.
Best regards.
Lee Xu commented on 07 December 2022
We have 2 Jira CLOUD instances. A bit extra info on the situation:
2 Jira Cloud instances, Iām only admin on 1 of them.
On our end, Start Date has customfield_ID 10015
On remote end, they have 2 Start Dates, ID 12202 and 12207, leads us to think we need to map to one of the IDs.
Support commented on 03 January 2023
Hi,
Is there any error message when you synchronize these custom fields? If so, may you please add the full stack trace?
Best regards.
Lee Xu commented on 06 January 2023
This is NOT an attempt to debug, but a request for how-to.
There were no error messages, we are looking for the script lines to enable such sync.
Support commented on 18 January 2023
Hi,
Allow to me share this below documentation for Jira Cloud custom field synchronization and review if this fits for you
https://docs.exalate.com/docs/how-to-sync-datedatetime-custom-fields-in-jira-cloud
Do not hesitate to contact us back if you have further questions.
Best regards,
Harold Cruz