External Task Sync Updates | Custory Changelog

We've improved linked task syncing so follow-up work in external tools stays more visible inside Custory after the task is created. Creating a task is only the first part of the job — teams also need to know whether it moved, stalled, changed scope, or quietly drifted away from the original customer problem. See this in action on any linked task in your [journey editor](https://app.usecustory.com).

## What's New

**Status sync.** Custory now keeps cached task status more current after work changes in Jira, Linear, GitHub, and Notion. Implementation progress stays visible without leaving the journey every time.

**Title sync.** If the external task changes title, Custory can reflect that change too — which matters when work evolves and the original wording no longer matches the current implementation scope.

**Notifications for external changes.** When linked work changes outside Custory, participants can be notified about important updates such as status or title changes. This helps teams avoid the common problem where implementation moves forward but the people managing journey context don't realize it.

## Why it matters

Journey work loses value when the map says one thing and the delivery tools say another. External task sync updates help keep those systems closer together so your team has a more reliable view of what is happening, what changed, and what still needs attention — without manually reconciling multiple tools.

We've improved linked task syncing so follow-up work in external tools stays more visible inside Custory after the task is created. Creating a task is only the first part of the job — teams also need to know whether it moved, stalled, changed scope, or quietly drifted away from the original customer problem. See this in action on any linked task in your [journey editor](https://app.usecustory.com).

## What's New

**Status sync.** Custory now keeps cached task status more current after work changes in Jira, Linear, GitHub, and Notion. Implementation progress stays visible without leaving the journey every time.

**Title sync.** If the external task changes title, Custory can reflect that change too — which matters when work evolves and the original wording no longer matches the current implementation scope.

**Notifications for external changes.** When linked work changes outside Custory, participants can be notified about important updates such as status or title changes. This helps teams avoid the common problem where implementation moves forward but the people managing journey context don't realize it.

## Why it matters

Journey work loses value when the map says one thing and the delivery tools say another. External task sync updates help keep those systems closer together so your team has a more reliable view of what is happening, what changed, and what still needs attention — without manually reconciling multiple tools.