Questions we get asked

Yes. No tiers, no seat count, no trial that expires, and no licence check inside the app that could stop it working. The pricing page sets out what free means here and what pays for it.

Two things, and neither is your data. WarrantySync is the free part of a wider asset lifecycle product line from ITSM Ltd, so it is worth more to us widely used than narrowly sold. And an app with real installations tells us what to build next, which a specification cannot.

There is no analytics, no telemetry and no beacon, so we learn that from the people who write to us and from nowhere else. The mailto: feedback link in the app’s footer is the entire listening mechanism.

A device serial number, sent to that device’s own manufacturer to ask when its warranty ends. Nothing else — no device names, no email addresses, no account ids, no issue content, no site URL.

That is structural rather than promised: the vendor adapters take a list of serial numbers and have no other parameter. The three hosts they may reach are declared in the app’s manifest and listed on the security page, and Forge refuses any address that is not among them.

No. Assets is a JSM Premium and Enterprise feature, and buying it in order to run this app would be the wrong way round. If you have it, point the app at an object schema and object type. If you do not, point it at a Jira project and issue type and it works against custom fields on any edition, including Free.

Dell is self-service: register for TechDirect API access with your Dell account and you get a Client ID and Client Secret. Approval usually takes a few working days.

Lenovo and HP are not self-service. Their credentials are issued by your account manager or reseller partner, and the settings page gives you the request email to send. Timescales are theirs rather than ours.

The app is useful while you wait: the pre-scan needs no credentials at all and tells you which of the three are worth chasing for your estate.

Against a stand-in for each, yes, and thoroughly: the request shapes, the authentication, the response parsing, the batching and the failure paths are all covered by the test suite. Against the manufacturers themselves, not yet — we hold no production credential for any of the three, which is the same problem the app is designed to work around for you.

Each will be verified against a live account before the app is listed on the Marketplace, and any that cannot be will be dropped from the listing rather than claimed. We would rather tell you this now than have you find it out.

Connect Dell and leave the others empty. A manufacturer with no credential saved is never contacted, and its devices sit in the “no data” tile reading Not checked yet. Worth knowing: that is the same wording a device gets before its first sync, so the tile does not distinguish “no credential for this manufacturer” from “not looked up yet”. The buckets view is where the per-manufacturer counts are.

Up to 10,000 devices. Past that the dashboard tells you it has reached the limit rather than showing a count it cannot stand behind. Work is paced through a queue inside an API budget you set, so a large estate takes longer rather than overwhelming your site.

No, and the protections are not settings you have to find. Nothing already expired ever gets a per-device issue. The first completed sync produces at most one summary issue. Ongoing issue creation is off until an administrator turns it on. There is a per-run cap, defaulting to 25, and anything over it is raised on the next run with the dashboard saying how many are waiting. A resolved issue is never re-raised for the same expiry date.

Yes, but the switch that does it is not the one you would guess. Turning off ongoingexpiry issues stops per-device and digest issues; it does not stop the single summary issue the first completed sync raises, which is deliberate — it is how you find out the app is working. To raise nothing at all, turn off Allow WarrantySync to create issues on the settings page. Leaving the expiry project unset also raises nothing, but keeps a warning on the dashboard until you choose one. You can also switch off write-back, in which case the app does not touch your device records either.

Never. Discovery reads what already exists and proposes a mapping, and an administrator confirms every field. If there is no warranty end date field, the app says what to create — a Date field called Warranty end — and offers to look again. A field the app invents is a field you are left with after the app is gone.

Because the app is not eligible, and implying otherwise seemed worse than explaining. The badge requires no egress of in-scope end-user data, and warranty lookup is egress: a serial goes to a manufacturer, and where a device is assigned to a person that serial can be personal data. The app declares it that way in its manifest, which is the conservative reading and the one that costs it the badge.

Everything the badge signals is nonetheless true, and every part of it is checkable on the security page.

Everything the app stored goes: settings, credentials, device records and counters. We have verified that on a real site, though the deletion is Forge’s to perform rather than ours to guarantee. The dates already written onto your devices and the issues already raised stay, because both are yours.

On reinstall, per-device de-duplication still works — its key lives in Jira, not in app storage — so a device that already has an issue for a given expiry date will not get a second. What does not survive is the app’s memory of the first run, so expect one repeat summary issue and one catch-up digest. That is the price of storing nothing outside Atlassian.

Any licensed Jira user, including the CSV export. It is a list of your hardware estate, so treat it with the same care as a Jira project anybody can browse. Every setting, credential and run control is administrators only, checked on the server on each action rather than in the page when it loads.

support@itsm-ltd.com for everything: support, evaluation, security questionnaires and data protection requests. The contact page explains what happens to each, and the support description has the response targets.

No. It is a Forge app, and Forge is Cloud only. There is no Data Center or Server edition and none is planned.