WarrantySync logo: a white tick on an indigo shieldWarrantySyncby ITSM Ltd
Menu
For your team

Four people, three surfaces

A dashboard in the Apps menu, a settings page in Jira administration, and a warranty card on the work item. Each of the four people below needs one of these surfaces, and none of them has a new tool to learn.
SurfaceWhere it isWho can open itWhat it is
WarrantySyncApps menuAny licensed Jira userThe estate dashboard: status tiles, the device table, the buckets view and the CSV export
WarrantySync settingsJira administration → AppsJira administrators onlyFive tabs, each saved on its own
WarrantyOn a Jira work itemAnyone who can view that work itemThe warranty card for the device the item is about
Role

IT asset manager

You are the person who gets asked how much of the estate is out of support, usually in a meeting, usually with about a day’s notice.

  • The estate in four numbers — expired, expiring, in warranty, no data — kept up to date by each run and rebuilt in full by the daily sweep
  • Press a tile to filter the table to it
  • Every “no data” device carries a reason, so the gap in the picture is itemised rather than estimated
  • Search by device name or serial number when somebody asks about one machine
Illustration of the dashboard, with sample data, with the Expired tile selected. The four tiles read Expired 97, Expiring within 60 days 38, In warranty 652, and No data 59. The Expired tile is outlined in blue and reads Filtering the list. Beneath the Devices tab, a Clear filter button sits beside Search, and the table shows expired devices, earliest warranty end first, from Expired 422 days ago to Expired 188 days ago.
Illustration, with sample data. A tile is a filter. The tile counts are maintained by each run and rebuilt from every record by the daily sweep, so between sweeps a tile can be a little ahead of the table beneath it.
Illustration of the Warranty panel on a service request, with sample data, titled Laptop battery will not hold a charge. The panel names the device ProBook 450 · LT-0266 and shows a grey No warranty found lozenge beside HP · 5CG3318KTZ, with the sentence The manufacturer returned no warranty for this serial number. Below are Last checked 13 Sep 2026, a Check now button and an Open device link.
Illustration of one no-data state. Five reasons a device can have no warranty data, and the card always names which one.
Role

Service-desk agent

You are deciding whether to raise an RMA or order a replacement, and the answer turns on whether this machine is still covered.

  • Status, end date, days remaining and service level, on the work item you already have open
  • The date it was last checked, so you know whether to trust it
  • Check now for a fresh lookup, once every fifteen minutes per device
  • No manufacturer portal login, and no waiting for somebody who has one
Role

Jira administrator

You are the one who will be asked what this app did to the site, and you would like the answer to be short.

  • It never creates schema. No custom field, no Assets attribute, no object type. Discovery proposes; you confirm
  • Five settings tabs, each saved on its own, so one change cannot resave another
  • Ongoing expiry issues are off until you switch them on, and the flood controls are not optional
  • Three things are written to your site, and they are listed on the How it works page
  • Uninstalling takes the app’s storage with it — verified on a real site, though the deletion is Forge’s to perform
Illustration of the Manufacturer credentials tab of the settings page. The Dell and Lenovo cards each carry a green Connected lozenge and the line Connected to Dell or Connected to Lenovo. Every credential box is empty, with the note A value is stored. Enter a new one to replace it. Each card has Save, Test connection and Remove buttons, and Lenovo's ends with the request email an administrator can send to their account manager. HP's card follows, out of frame.
Illustration, with HP’s card out of frame. Credentials go into Forge’s encrypted secret storage. The app reads them to authenticate and returns them to nobody: a saved box stays empty, and no log line, export or API response gives one back.
Role

Security reviewer

You have been sent an app to approve and you would like to know what it can reach, what it sends, and who else is involved.

  • Three declared hosts, and Forge will not let the app open a connection to anything else
  • One data type leaves: a device serial number, to that device’s own manufacturer
  • No analytics, no beacons, no licence check. There is nothing to opt out of because nothing is being collected
  • All compute and storage are Forge-hosted, but the app is not eligible for Atlassian’s data residency pinning, and serial numbers sent to a manufacturer leave your region
  • A cloud security statement, a DPA and a privacy policy written to be read
The security detailCloud Security Statement

Who can reach what

There are three cases here, and only the first is what people assume. Every setting, credential and run control is checked on the server when it runs, not in the page when it loads. Reading is not checked at all. And Check now is neither: it is offered wherever the panel renders, which means anyone who can view the work item, and the server acts on the device id it is given rather than re-deriving who is asking — which is why it is rate-limited. This table is what actually happens rather than what a button looks like.

ActionWho
Open the dashboard, filter it, search itAny licensed Jira user
Export the estate to CSVAny licensed Jira user
See the warranty card on a work itemAnyone who can view that work item
Press Check now on the warranty cardAnyone who can view that work item
Change any settingJira administrators
Connect or remove a manufacturerJira administrators
Start a sync, force a re-check, re-run the pre-scanJira administrators
Turn ongoing expiry issues on or offJira administrators

Reading is open

The dashboard and the CSV export are available to any licensed Jira user. It is a list of your hardware estate — treat it as you would a Jira project people can browse. A non-administrator is told plainly why the run controls are unavailable, in text, rather than shown four disabled buttons and left to press one.

Acting is not

Every setting, every credential and every run control is administrators only, enforced server-side. Check now is the one deliberate exception: any viewer of a work item may press it, because the repair-or-replace decision belongs to whoever is holding the ticket. It spends a real manufacturer lookup, so it is rate-limited to once every fifteen minutes for a given device.

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.

Register your interestBook a walkthrough