Overview Customers need activity logs to accurately distinguish between different task states and clearly identify when a task was created automatically by Limble rather than manually by a user. This is especially important for Min Qty tasks generated when inventory reaches the Part Qty Threshold. Current Limitations •…
Overview The customer needs a way to remove specific inventory quantities while preserving the correct historical cost layer. In this case, recently received parts were incorrect and discarded, but the associated Bill and PO were valid and needed to remain intact for accounting history. The current manual quantity…
Overview The customer wants Limble to protect manually entered pricing during the Purchase Order workflow. Currently, if a user enters a rate first and then selects or changes the vendor, Limble can automatically replace the manually entered rate with the part/vendor price. The customer expects either the manual rate to…
Overview The customer needs exports from Open Tasks → Bulk Export to be immediately usable for reporting and analysis. The current export requires significant manual cleanup and does not include the Asset ID as a dedicated field. While Limble’s submitted feedback captured the missing Asset ID, the broader issue is that…
Overview When users paste content into the Work Request Portal’s “How can we help?” field from applications such as Microsoft Teams, Limble currently retains formatting and hidden characters. This can cause the field to exceed the 1,000-character limit even though the visible text appears to be well below the limit. The…
Overview When Limble warns that a part already exists on an open Purchase Order, the customer wants the warning to include whether the item has already been received and how many units remain outstanding. Current Limitations • The warning indicates that the item exists on an open PO but provides limited receiving context.…
Description A part can be configured with inventory minimum and maximum values that appear logically reversed, such as a minimum of 2 and maximum of 1. The configuration can be saved, and the reorder workflow can subsequently add the part to a Purchase Order without producing a valid order quantity. Steps to Recreate Open…
Overview When a Purchase Order cannot proceed because of an invalid quantity, the customer wants Limble to identify the exact affected line and explain what is wrong rather than displaying a generic quantity warning. Current Limitations • Validation can state that a quantity is required even when a quantity is already…
Overview The customer wants a way to recover from accidental edits or deletions while building or modifying a Purchase Order. Current Limitations • Accidentally changed values cannot easily be restored to their prior state. • Deleted PO items do not have an immediate undo option. • Users may not remember the previous…
Overview The customer wants normal page scrolling to remain safe while working in Purchase Orders. When the cursor is positioned over an active numeric input, browser-native behavior can increase or decrease the value instead of scrolling the PO. Current Limitations • Mouse-wheel movement over an active number field can…
It looks like you're new here. Sign in or register to get started.
