1
0
-1

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.

  1. Harold Oconitrillo

    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.

  2. Lee Xu

    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.

  3. Support

    Hi,

    Is there any error message when you synchronize these custom fields? If so, may you please add the full stack trace? 

    Best regards.

  4. Lee Xu

    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.  

  5. Support

    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


CommentAdd your comment...

1 answer

  1.  
    2
    1
    0

    Hi Harold


    Assuming the name of your custom field is "Start Date":


    On the Source Side (Outgoing sync):

    replica.customFields."Start Date" = issue.customFields."Start Date"
    
    


    
    

    On the Destination Side (Incoming sync):

    issue.customFields."Start Date".value = replica.customFields."Start Date".value


    Please let me know how it goes.
      CommentAdd your comment...