Workfront Fusion release activity: Week of October 5, 2026

This page describes all enhancements made in Adobe Workfront Fusion the week of October 5, 2026.

For a list of all recent changes, see Adobe Workfront Fusion release activity.

For a list of recent bug fixes in Workfront Fusion, see the Workfront Maintenance Updates page and check for any updates labeled Workfront Fusion Maintenance Update.

Jira connector: New service account connection types

To make it easier to create Jira connections that match how your team authenticates, we’ve added two new connection types to the Jira connector: Service account API token and Service account OAuth 2.

These options let you create connections for automation that should run as a dedicated Jira service account instead of a personal user account. Use Service account API token when your Jira service account authenticates with an API token, and use Service account OAuth 2 when your environment uses OAuth 2 for the service account.

Basic and OAuth2 connection types are still available.

For more information, see Jira modules.

New Create multiple annotations module available for Veeva Vault connector

To make the Create multiple annotations module easier to use, we’ve updated it to a new module. Now, you can select fields for placemarks, references, and other annotations fields before you provide values, making configuration simpler and focused only on the values you prioritize.

The previously available Create multiple annotations module is still available, marked as “Legacy.”

For more information on Veeva Vault modules, see Veeva Vault modules.

Add additional retry status codes to the HTTP > Make a request module

To give you finer control over HTTP request retries, we’ve added and Additional Retry Status Codes fields to the HTTP > Make a request module.

Now , you can define custom HTTP status codes that should be treated as retryable, in addition to the built-in retryable codes (408, 429, and all 5xx responses). For example, you can now make a 422 response retryable. T

For more information, see HTTP > Make a request module.

Add signed JWT authentication to HTTP requests with the HTTP > Make a JWT request module

To make it easier to call APIs that require signed JWT authentication, we’ve added the HTTP > Make a JWT request module.

This module works like the standard HTTP > Make a request module, but it automatically generates and signs a JSON Web Token from the claims you provide and includes it in the request, by default as an Authorization Bearer token. This helps you authenticate to services that require short-lived JWT-based access without creating a separate token-generation step in your scenario.

For more information, see HTTP > Make a JWT request module.