Can I sync only selected fields?

    Yes, you have complete control over which fields to synchronize through your outgoing and incoming sync scripts. 

    Outgoing sync control: specifying fields to share

    In the outgoing script, you specify exactly which fields to include in the replica object by selecting only the properties you want to share. Fields not included in your outgoing script never leave your system, giving you precise control over data exposure.

    For example:

    • You might sync summary, description, and priority while excluding sensitive fields like internal comments, financial data, or customer information.
    • You can use conditional logic to sync additional fields for high-priority items, or customize field sets for different projects.

    Incoming sync control: deciding which fields to apply

    Incoming scripts provide similar control over what data to accept and apply locally. Even if the remote side sends multiple fields, your incoming script decides which ones to write to your work items.

    You can:

    • Ignore certain replica fields

    • Map incoming fields to different local fields

    • Apply transformations before storing values in your system

    This allows you to tailor incoming data handling based on your needs, ensuring data consistency without risking unwanted overwrites or errors.

    Field-level control for cross-company integrations

    This field-level control is particularly valuable in cross-company integrations where each organization has different data sharing policies. Your team might choose to share only status updates and comments while keeping internal notes, time tracking, and budget information private. The receiving organization independently controls which of your shared fields they want to apply to their work items.

    One-way field synchronization

    You can also implement one-way field synchronization where a field only flows in a single direction. For instance, you might send priority values outgoing but never accept incoming priority changes, keeping control over that attribute on your side. Different fields can have different synchronization directions within the same connection.