While assets in Limble have field-level change history available, complete with a visible history icon next to each field, parts do not have the same functionality. Most fields on parts have no history tracking at all, and even for those that do, there is no icon or direct access. Instead, users must open the general log page to see changes, which makes it much harder to quickly audit or verify data updates.
Current Limitations
- Inconsistent Experience: Assets have history icons for each field, but parts do not.
- Missing Field-Level History on Parts: Many part fields are not tracked at all, leaving gaps in accountability.
- Indirect Access: For fields that are tracked on parts, users must navigate to the log page rather than seeing history inline.
- Audit Blind Spot: Makes it difficult to trace who changed what, when, and why at the part level.
General Example
- A user updates the cabinet field on a part. Later, when another user wants to know who moved it, there is no history icon or inline history available. They must go to the log page, and in this case, the field isn’t tracked there at all, creating a dead end.
Requested Enhancements
- Extend Field-Level History to Parts
Ensure all key part fields (e.g., cabinet, location, thresholds, type) have history tracking. - Add History Icons for Parts
Display the same “View the history of changes” icon next to fields on parts, consistent with assets. - Inline Access Instead of Logs
Let users click directly on the history icon to see who changed a field, when, and what the old/new values were, without going to the log page.
Business Value
- Consistency: Aligns the parts experience with assets, reducing confusion.
- Transparency: Makes field-level data history easy to find and trust.
- Audit Readiness: Supports compliance, traceability, and troubleshooting by surfacing detailed change logs.
- Efficiency: Saves users from unnecessary navigation into the logs page, speeding up audits and day-to-day work.
