Issues and the staff report form
A fault, a change request, new equipment or something lost, reported against the asset it is about and tracked to done.
What it does
An issue is something someone wants looked at. Most are about an asset, and the asset's page lists its issues alongside its history. Each issue has a status, a category you define, a priority, an assignee and a thread of notes. Tagaris is an asset register, so issues are kept deliberately small: there are no SLAs, queues, approvals or email-to-issue.
- An Issues page with search and filters, an Issues card on every asset, and a Report an issue button in the asset header
- Categories are yours: a new organisation starts with Fault, Change request, New equipment, Lost or stolen and Other
- Reporting can set the asset to Repair; resolving offers to put it back and to log the repair, with its cost, in the maintenance records
- New issues appear once in the daily digest and post to Slack, Teams or a webhook as they arrive
- An issue linked to an asset can be raised to Jira; the ticket shows on the issue and the asset
- Issues in the REST API, the organisation data export and the mobile app
The full walkthrough, with the limits on the staff form and what can go wrong, is in the issues guide.
The staff form
Most people who notice a fault have no Tagaris login and should not need one.
Switch it on
Settings, Issues. You get a long private link to put on your intranet or print as a QR code by the printers. The form asks for a name, an email address, what it is about, an optional asset tag, where the item is and what is wrong. Making a new link retires the old one.
Or scan a label
With the form on, someone who scans an asset's QR label while signed out sees the sign-in page with one addition: "Not in IT? Report an issue with this item". The form opens with the item already chosen, so every label already on your kit is a way to report a fault, with nothing to reprint. IT staff who sign in from the same page land on the asset they scanned.
Give it its own address
An organisation can put its form on a hostname of its own, help.example.com, with its own name and logo. Route the hostname to the same container in your reverse proxy and the form is served at its root. The hostname serves nothing else. On a server with several organisations, each can have one.
Built to give nothing away
It is the one page in Tagaris that works without a login.
- It shows nothing from the register. Opened from a label it shows that item's asset tag, which is printed on the label the person is holding, and nothing else.
- It says the same thank-you whether or not the asset tag matched, so it cannot be used to find out what you own.
- One address can send five reports in ten minutes, and the form accepts 200 a day per organisation. A hidden field catches scripts. There is no file upload.
- Nothing is emailed to the address typed into the form unless an administrator chooses to tell the reporter the issue is resolved.
- No third-party service is involved: no CAPTCHA, nothing leaves your server.
Who can do what
Editors and administrators report, triage and resolve. View only means exactly that, so a view-only person who should be able to report gets the "Report issues and add notes" permission through an access group, or uses the staff form. Triage (status, priority, category, assignee, linking an asset) is a permission of its own, so a service desk group can work issues without editing assets. Administrators delete issues and manage the categories and the staff form. Every step is written to the asset's history.
Roles, access groups and the permissions list are in roles and access; the Jira hand-off is on the Jira integration page.
Common questions
Is this a service desk?
No. Issues are kept small: a status, a category, a priority, an assignee and notes. There are no SLAs, queues, approvals or email-to-issue. If you run a service desk already, keep it and link its tickets from the asset page, or hand an issue to Jira.
Can staff report a fault without a login?
Yes. Switch on the staff form and anyone with the link can report an issue. Scanning an asset's QR label while signed out offers the form for that item, and the form can have a hostname of its own.
What does the staff form give away?
Nothing from the register. It says the same thank-you whether or not the asset tag matched, the link is unguessable and can be retired, there is no file upload, and nothing is emailed to the address typed into it unless an administrator chooses to tell the reporter it is resolved.
Who can report and who can resolve?
Editors and administrators report, triage and resolve. A view-only person needs the Report issues permission through an access group, or uses the staff form. Administrators delete issues and manage categories.
Does it need a paid plan?
No. Issues and the staff form are on every plan, the free tier included.
Every label on your kit becomes a way to report a fault
The live demo has issues loaded against its assets. Issues and the staff form are on every plan, the free tier included.