Releases · Version 2.1.0

What changed, and how it reaches you

The app is not yet listed on the Atlassian Marketplace, so there is nothing here to upgrade from. This page is the record of what each version changed, published from the day there is something to record rather than the day it becomes convenient.

How updates reach you

Once the app is listed, a new version is deployed to the Marketplace and takes effect for installed sites with no upgrade to schedule, no downtime window and no compatibility matrix to check. With two exceptions: a major update, and any update that adds a permission scope or a manufacturer host, requires approval by your Atlassian site administrator. That approval is what stops a fourth egress host appearing quietly.

Cadence

Releases will be made when there is something worth releasing rather than on a fixed date. Fixes for defects that affect correctness — a wrong status, a duplicated issue, a failed run — are made as soon as they are ready.

Notice we give

A change that would alter behaviour you may depend on — a default, a permission, a removed capability — will be announced in advance by email to the technical contact on the installation, on the terms in the support description. Fixes and additions that do not change existing behaviour ship without notice.

Versions follow semantic versioning, and every release has a note below, newest first. A major version would be reserved for a change that requires you to do something.

What each version carries

Latest1 October 2026

2.1.0 – Privacy and clarity

New Features

None in this release.

Improved Features

The settings page now tells an administrator when JSM Assets is chosen as the device source but is not available on their site, and suggests Jira work items instead.
The privacy policy, terms, security statement and data processing agreement now state plainly that WarrantySync does not support Atlassian data residency, and that serial numbers sent to a manufacturer leave your region.

Security Fixes/Patches

If you set a default assignee for expiry issues, WarrantySync now reports that account to Atlassian each week and removes it from its own records when the account is closed.
Updated third-party components to clear published security advisories.

Defect Fixes

None in this release.

29 September 2026

2.0.0 – Baseline

New Features

A dashboard, a settings page and a warranty card on each issue, all built into Jira with nothing to install elsewhere.
Choose where your devices live: JSM Assets (Premium and Enterprise sites) or Jira work items (every edition). If Assets cannot be reached, WarrantySync falls back to Jira work items and tells you why.
Guided field mapping. WarrantySync suggests which fields hold the serial number, manufacturer, model and warranty end date, and asks an administrator to confirm.
Warranty look-ups for Dell, Lenovo and HP.
A pre-scan that needs no manufacturer credentials. It counts your estate by manufacturer and shows the devices it could not classify, so you know what to expect before connecting anything.
A daily expiry check that works from the warranty end date already stored, so warnings never wait on a manufacturer.
Expiry issues that stay quiet: none for warranties that have already expired, at most one summary on the first sync, ongoing issues only if you switch them on, a limit on how many are raised per run, and no repeat issue for a date you have already resolved.
Export the current estate as CSV, ready to copy into a spreadsheet.
Four user guides, one each for administrators, the dashboard, the issue panel and troubleshooting.

Improved Features

Devices with no serial number, or no warranty date, now appear in the estate so you can see and fix them.
The dashboard no longer shows run controls to people who cannot use them.
Pressing Enter in the device search box runs the search.
Error messages say what went wrong and what to do about it. A field you still need to fill in is now reported as exactly that.

Security Fixes/Patches

Manufacturer credentials are held in Forge encrypted storage and are never shown back to anyone.
Every settings change checks that you hold Jira administrator permission.
Only serial numbers are sent to manufacturers, and only to the three manufacturer sites WarrantySync declares.
WarrantySync does not request access to user profiles, because it never needs them.

Defect Fixes

Syncs, pre-scans and expiry checks now complete on a live site. Previously the background work behind them could stall before finishing.
Estates of more than 25 devices no longer fail part-way through a run.
Records for devices with a blank serial number or warranty date are no longer rejected.

Something looks wrong in a release

If a version changed something you relied on, or a fix did not fix it, write to support@itsm-ltd.com with the version and what you were doing. Priority definitions and response targets are in the Support and Maintenance description, and the troubleshooting guide lists every message the app can show.

Find out what is out of warranty before somebody else does

It installs with no credentials and counts your estate on the first run, so you know the size of the problem before anybody has to request API access. It is free, and there is no licence check to fail.