You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a computer first gets loaded into the system, it usually hasn't been loaded with an OS yet, and sometimes nobody remembers to go in and update the system when an OS actually has been loaded.
Describe the solution you'd like
A checkbox on the custom field properties (ala "Automatically add this to every new fieldset" or "This value must be unique across all assets") that says something to the effect of "Show field on checkout form" so that it can be easily updated while we can easily verify it
Describe alternatives you've considered
Our current solution is to basically just use spreadsheets to quickly get down the data which tends not to result in the inventory being as up-to-date as it should be
Additional context
There is a three year old feature request for a similar feature (#9515), it was kinda vague and unspecific about the feature which is why I'm opening a new issue instead of building on that old one
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a computer first gets loaded into the system, it usually hasn't been loaded with an OS yet, and sometimes nobody remembers to go in and update the system when an OS actually has been loaded.
Describe the solution you'd like
A checkbox on the custom field properties (ala "Automatically add this to every new fieldset" or "This value must be unique across all assets") that says something to the effect of "Show field on checkout form" so that it can be easily updated while we can easily verify it
Describe alternatives you've considered
Our current solution is to basically just use spreadsheets to quickly get down the data which tends not to result in the inventory being as up-to-date as it should be
Additional context
There is a three year old feature request for a similar feature (#9515), it was kinda vague and unspecific about the feature which is why I'm opening a new issue instead of building on that old one
The text was updated successfully, but these errors were encountered: