v1.0.71

TSANet Connect for Zendesk v1.0.71

Security note: this release was NOT covered by a current security review. See the release run summary for details.

Fixed: TSANet Partner and TSANet Respond By changed and reverted on every partner reply

The background flow (ZIS) and the sidebar app wrote these two fields with different rules, and each overwrote the other:

• TSANet Partner: on inbound collaborations, the background flow wrote your own company name instead of your partner's. The sidebar wrote the partner back the next time an agent opened the ticket.
• TSANet Respond By: the background flow kept writing the deadline after the case had been acknowledged, while the sidebar clears it.

Each partner reply added a change and a revert to the ticket timeline. Tickets nobody had opened since could also be left showing your own company as Partner.

The background flow now follows the sidebar's rules:

• Partner is your partner's company: the submitting company on inbound collaborations, the receiving company on outbound ones.
• Respond By shows the acknowledgment deadline until the case is acknowledged, then it is cleared.
• It writes a field only when its value actually changes, so a partner reply that changes nothing adds nothing to the timeline.

Tickets already showing the wrong Partner correct themselves on the next TSANet event for that case. The tsanet_updated tag is still applied as before, so retention selectors keyed on it keep working. Reported by a member; thank you for the clear report. (#235)

What to do

• Update the app in Admin Center → Apps and integrations → Zendesk Support apps. Private apps do not update automatically.
• Then redeploy the ZIS bundle: open the app's deploy screen, select Re-check, then Deploy. The fix is in the bundle, so updating the app alone does not change this behavior.
• If you install the bundle by hand (the zis/README.md path rather than the deploy screen): upload zis/tsanet_connect_bundle.json from the v1.0.71 tag (the same file ships in the zip as assets/tsanet_connect_bundle.json), then reinstall the job specs as that guide describes.

Security review status

The release gate marks this build "not covered". The changes in this release were reviewed, with no findings. The flag comes from an automated check that fails once a TSANet deprecation is within 90 days. The connector still uses TSANet's v1 webhook endpoints, which are removed after 2027-01-01. Moving to v2 webhooks is tracked in #101, and we will publish migration steps before that date.

Internal

• A CI test now runs the bundle's update expression through jq against fixtures that mirror the sidebar's rules. The same paths were confirmed on a Beta-paired test instance before release.

Verification

• SHA-256 checksum and SLSA build-provenance attestation are attached; verify with gh attestation verify <zip> --repo tsanetgit/Zendesk_App.