If we cancel a work order because it's a duplicate, we also leave it for transparency rather than deleting it. How do you handle these so that it's not in the requests anymore? We have been moving them to a planned work state so that they aren't causing clutter in the recent requests. Just looking for other options or best…
The customer needs a more efficient and transparent way to assign multiple assets to a PM template. They want to easily view all assets already assigned to a template, directly within the assignment process, and avoid unnecessary navigation between screens. The current workflow makes it difficult to track assignments and…
Limble’s current tag functionality is limited—tags are created and applied manually with no centralized management, bulk editing, or usage reporting. This leads to inconsistent tagging, inefficiencies, and data clutter as our system scales. Current Limitations - No centralized view or control over all tags. - Tags must be…
Has anyone known a way to fast search the limble system of duplicate parts that doesn't necessarily require me to export all the data to an excel spreadsheet?
Users are experiencing inconsistent behavior when navigating Limble CMMS after being logged out due to inactivity. After re-authenticating, sometimes the system returns them to the last page they were on (e.g., a specific asset or task page), but other times they are redirected to the Global Dashboard instead. This breaks…
Users need a way to log and track core charges on parts (e.g., motors) that are received and then returned to the supplier for a refund. Core charges are common in parts workflows, and without proper tracking, teams cannot confirm whether a refund was received within the required timeframe. Current Limitations No Core…
Users need a formal process to handle credits issued by vendors for defective or returned parts. The workflow should account for whether the credited part is removed from inventory (if unusable) or remains in stock (if still usable), while properly recording the credit in financial records. Current Limitations No Credit…
Users need a formal, trackable way to process returns for purchased items, whether the Purchase Order (PO) is closed or partially received (open). The process should also support recording related charges, such as restocking fees, without requiring manual workarounds that distort records or disrupt workflows. Current…
The current system display logic can cause confusion by showing parts as available for a task even when the actual inventory is zero. This happens because the system combines general stock with parts tied to Purchase Orders (POs) when calculating availability. As a result, users may mistakenly believe a part is in stock…
Users need the ability to generate a shareable link for Purchase Orders (POs) within the system. Currently, POs can only be shared by printing an external or internal view, but there is no option to copy or send a direct link. Having shareable links would make collaboration and communication around POs much easier. Current…
It looks like you're new here. Sign in or register to get started.