Skip to main content

Why is a recorded issue not coming through in my Issues register?

Learn why some of your recorded issues might be missing from your Issues register

Adriana De Souza avatar
Written by Adriana De Souza
Updated over 5 months ago

One of Gearbelt’s powerful features is that it lets your team log issues across all assets, making it easier to track and resolve issues. The Issues register gives you a clear view of every issue and its current status. Generally, issues will be recorded while conducting pre-starts, inspections and service checks.

Sometimes, you might notice that certain issues aren’t showing up in the Issues register. Here's why that could be happening - and how you can fix it.

There are two types of fields in forms that let you record issues in a way that ensures they’re properly logged and added to the asset’s Issues register:

  • The Issue option in the Check field

  • The standalone Issue Selector field

Note: You can only use one Issue Selector field in your template. You'll be able to recorded multiple issues through that field

⚠️ Issues recorded in a form in any other way will only appear on that form and won’t be visible elsewhere

To summarise, avoid recording issues in:

❌ Tables

❌ Checkboxes

❌ Dropdowns

❌ Text fields

Did this answer your question?