Connector
Jira connector
November 13, 2026

Jira connector. Sync Jira Cloud issues two-way with any other app, along with Users, Sprints, and Versions. Sign in with Atlassian, no API token needed. Issues are titled by their summary everywhere a record's name shows.
Also this week
- Sign in with Copper. Copper connections now sign in through Copper, so connecting no longer takes an admin's API key. Pasting a key and email still works, and existing connections carry on as they are. Live Export gets the same sign-in.
- Shopify Customers and Orders in Live Export. Customers, Orders, Order Line Items, and Order Shipping Lines export on every Shopify plan, with names, emails, phones, addresses, and each order linked to its customer. A token that's missing a scope fails up front with the scopes named (
read_customers,read_orders,read_all_orders). After the first run, these tables pull only what changed. - Connecting apps over MCP happens only in the browser.
sync_createandlive_export_createtake connector names and hand back a link where a person signs in, so credentials never pass through an agent's chat. - Zendesk's subdomain field takes whatever you paste.
acme,acme.zendesk.com, or the full URL all connect. - A heads-up about archived Zendesk tickets. Zendesk archives a ticket about 120 days after it closes, and the sync sees that as a delete. The warning before a sync's first activation says so, and that choosing Ignore on the Pending deletes tab keeps the row.
- Zendesk pushes report what Zendesk kept. When Zendesk stores a value differently than it was sent (trimmed text, sorted lists, reformatted numbers and dates), the other side gets the stored value instead of drifting.
- An Asana task the connected account can't see no longer asks you to reconnect Asana.
- Framer records with an empty number, checkbox, or option field create and update. Framer has no empty value for those, so they're written as 0, unchecked, or the first option.
- Zendesk: a user's phone can change to a number another user already has, a tags change sent with a multi-select keeps both, and an email change on a user with a verified address shows up.
- An error page from Memberstack is no longer read as a member being deleted.
- A HubSpot property named "constructor" shows up in the schema.
- A Jira push refused over fields only other issue types take goes through without them, so the rest of the change lands.
- Saving mappings while a removed table is still being cleaned up no longer fails.
Discover more