Diffuse 0.10.2 · Connect your Jira account

Diffuse 0.10.2

This release fixes Jira sign-in for the shared extension ZIP. Official downloads now have one stable extension identity, approved by the hosted connection service. Each person connects their own Atlassian account; Jira connections and reviews are not shared between users.

Install and connect

1. Download Diffuse-0.10.2.zip and unzip it into a permanent folder.
2. Open chrome://extensions, enable Developer mode, choose Load unpacked, and select the unzipped Diffuse folder.
3. Open Diffuse → Settings → Jira connections → Connect Jira and sign in to Atlassian.

No installation-ID submission, API token, local server, or personal OAuth app is needed. Your Jira permissions and your organization's app policy still apply. Atlassian may display an unreviewed-app notice.

Keep reviews from 0.10.1 or earlier

The new identity has separate browser storage. Before upgrading, export each review you want to keep using ⋯ → Export review. Keep the old installation and folder intact; install this version separately and import your exports with Load review. Reconnect Jira and optional AI/Figma settings. Disable the old copy after checking your imported reviews. Do not replace the old files expecting Chrome to migrate their storage.

Future official versions will keep this identity and can be updated in place, using Reload without uninstalling. The release script also leaves the legacy unpacked installation untouched.

Other changes

• Unsupported installations get a specific update message instead of the generic service-unavailable error.
• Settings use normal sign-in guidance and reserve the extension ID for support diagnostics.
• A confirmed expired or removed Jira connection clears its cached account details; temporary network failures retain the connection.
• The hosted service includes scheduled Atlassian account-data reporting and cleanup. See the privacy notice.

Fresh-profile and different-folder Chrome tests verify the shared ID and preservation of exported review text and screenshots. Provider tests cover OAuth isolation and failure handling. See Jira verification for live checks and remaining coverage; these tests do not claim a completed sign-in on every recipient's account or a real ticket creation.