Administrator guide
Set the app up: choose where your devices live, map the four fields, connect a manufacturer, set the warranty rules, and decide what happens at expiry.
For Jira administrators
Set the app up: choose where your devices live, map the four fields, connect a manufacturer, set the warranty rules, and decide what happens at expiry.
For Jira administrators
Read the estate: the four tiles, the pre-scan and what it tells you, running a sync, the device table, searching, exporting, and the expiry-issues tab.
For Anyone with a Jira licence
Look after one machine: adding the card, how it finds the device, the four statuses, the five reasons there may be no warranty to show, and Check now.
For Anyone who can view the work item
How to read an error from this app, then every message it can show and what to do about each one.
For Whoever is looking at the message
| If | Read | Start at |
|---|---|---|
| You are installing it | Administrator guide | Start at “Before you start”. The first two sections get you to a working pre-scan with no manufacturer credentials at all. |
| Somebody else installed it | Dashboard guide | Start at “Reading the estate”. Most of what is there needs no administrator rights. |
| You are on a ticket about one machine | Issue panel guide | Read “Reading the card” and “The four statuses”. Two minutes, and it is the only part you will need. |
| You are looking at a message you do not recognise | Troubleshooting | Every message the app can show, what it means, and what to do about it. |
The screenshots are of a real Jira site running the app, not mock-ups. The estate in them is synthetic: about two hundred devices generated by the repository’s own seeding tool, with serial numbers of the form SEED000123.
They were taken on 8 September 2026, on a development build, so they show aDEV label and the product’s name as two words, “Warranty Sync”, which was corrected the next day. They are due to be taken again on a production site with a realistic estate.
The warranty dates come from a stand-in for the three manufacturers rather than from Dell, Lenovo and HP themselves. No production credential for any of the three existed when the guides were written, and a run with no credentials puts every device into the same “no data” state — which would have documented a product that looks broken rather than one that works. The dates are representative rather than genuine. Everything else on screen is what the app actually produced on a real site: every layout, every message, every count, every issue raised.
Some states are described in words rather than photographed: the storage-limit banner, which needs an estate of more than 10,000 devices, and the five “no warranty data” reasons on the issue panel. Their wording is quoted from the app.
Every screenshot but one was taken in Jira’s light appearance; the first-use consent screen was taken in dark. The app follows your Jira theme, and renders correctly in both.
Read the administrator guide end to end and you will know exactly what the app will and will not do to your site before it does any of it. That is the order we would want it in.