User guide
Issue panel guide
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.
The warranty card sits on a Jira work item and answers one question: what is the warranty position of the machine this item is about?
Anyone who can see the work item can see the card, and anyone who can see it can press Check now. It is not restricted to administrators.
Adding the panel to a work item
The panel does not appear by itself. On the work item, open the app actions menu — the button beside Add — and choose Warranty. It then stays on that work item.
This is Jira’s behaviour for app panels, not a WarrantySync setting, and it is per work item.
How the card finds the device
WarrantySync tries three things, in order:
- The work item is itself a device record. If your devices are Jira work items, this is the normal case and nothing needs configuring.
- The Assets object field, if an administrator has mapped one. Used where devices live in Jira Service Management Assets and the work item links to the object.
- The serial number field, if an administrator has mapped one.
Both mapped fields are optional. With neither set, the card only appears on work items that are themselves device records.
One consequence is worth knowing: the card reads what the last sync stored. It never contacts a manufacturer just to draw itself. A device that has never been through a sync has nothing to show, even if the work item is plainly a device.
Reading the card
From the top:
| Line | What it is |
|---|---|
| Device name | The device record’s name |
| Status lozenge | One of the four statuses, colour and words together |
| Manufacturer · serial | What was sent to the manufacturer — the serial and nothing else |
| Warranty ends … (N days) · service level | The stored end date, days remaining, and the entitlement if the manufacturer gave one |
| Last checked | When the sync last looked this device up |
The four statuses
The same status model as the dashboard: Expired, Expiring (inside the administrator’s warning window), In warranty, and No data. Status is worked out from the stored end date every time the card is drawn, so it stays right as the date passes.
When there is no warranty to show
The card says which of the five reasons applies, in these words:
| Reason | What the card says | What to do |
|---|---|---|
| Never synced | Not checked yet. Use Check now to look this device up. | Press Check now, or wait for the daily sync |
| No serial number | This device has no serial number, so it cannot be looked up. | Put the manufacturer’s service tag on the device record |
| Manufacturer not covered | Warranty lookup covers Dell, Lenovo and HP. | Nothing to fix. The device is counted but never looked up |
| Manufacturer had no record | The manufacturer returned no warranty for this serial number. | Check the serial is the manufacturer’s own service tag, not an asset label |
| Manufacturer unreachable | Could not reach the manufacturer. The daily sync will retry. | Nothing. It retries by itself |
Of these, only the “no device linked” state below and the in-warranty card above were photographed for this guide. The wording in the table is quoted from the app rather than from a screenshot.
Check now
Check now looks the device up immediately, rather than waiting for the daily sync. It spends a real manufacturer lookup, so it is limited to once every fifteen minutes for a given device. Inside that window the button is unavailable and the card says when it becomes available again:
Checked 13 minutes ago. Check now becomes available once fifteen minutes have passed.
Anyone who can see the work item can press it. There is no administrator check on this control, by design — the person holding the broken laptop is rarely a Jira administrator.
Open device goes to the underlying device record.
When the panel cannot help
The card says no device is linked and explains that WarrantySync matches a work item to a device by the fields set on the settings page.
On a fresh installation this also appears on work items that are devices, simply because no sync has stored anything yet. Run a sync and the card fills in.
If the card cannot load at all, it says so and offers Try again.
The issues WarrantySync raises
When expiry issues are switched on, the app raises Jira issues in the project an administrator chose.
The first completed sync raises one summary issue and nothing else.
It states how many devices have already expired and how many are inside the warning window, and says plainly that nothing further will be created unless an administrator turns ongoing expiry issues on.
After that, and only after the dashboard switch is on, per-device issues appear.
Each one carries:
- A machine key in the summary —
[WS:<deviceId>:<warrantyEnd>]. This is how the app recognises its own work and avoids raising the same issue twice. Leave it in place. - Two labels —
warranty-syncon everything it raises, andws-<deviceId>identifying the device.
Those labels join your site’s shared label namespace, so they appear in label pickers for everyone, not just in this project. Deleting the issues removes the labels from those pickers, because Jira derives the namespace from issues — but it does not remove them from any saved filter, board, dashboard gadget or automation rule somebody built on them in the meantime.
A device whose warranty has already expired never gets a per-device issue, and a resolved issue is never re-raised for the same expiry date.
The warranty date on your device record
While write-back is switched on, each successful lookup writes the warranty end date onto the device record, into the date field an administrator mapped and nowhere else. In the card screenshot earlier in this guide it is the WS Warranty end field, in the work item’s own Details panel.
That date is yours. It stays on the record whatever later happens to the app, including uninstalling it.