Until now, nothing told you an integration was about to break. A token expired, the sync stopped, and the first sign of trouble was usually someone noticing that an issue in Jira or Azure DevOps and its Craft.io item had drifted apart. By then teams had been working on both sides for hours or days, and someone had to reconcile the difference by hand.

With this update, Craft.io warns your workspace admins ahead of an expiry and flags the risk to everyone working in the workspace, so your integration tells you it needs attention before it stops syncing.

To enable these alerts, set the renewal date when you create a connection, or add one to an existing connection from Update Connection in the integration panel.

Rotating a token used to mean repeating the same update in every workspace that shared the Jira or Azure DevOps connection, and any workspace you missed stayed broken until someone noticed the sync had stopped.

Now, when you update a token and the same integration user is connected elsewhere on your account, Craft.io asks whether to apply the change everywhere, so one update can cover every matching connection at once.

Connecting an on-premise Jira instance meant handing over a personal username and password. That tied the integration to one person's own login, so a password change or an account lockout took the sync down with it, and teams were left with gaps in their data before anyone worked out why.

You can now connect on-premise Jira with a personal access token instead, from the same connection setup screen. The token belongs to the integration rather than to someone's day-to-day account, so routine password changes and lockouts no longer break the sync.