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
What is the problem you are trying to solve with this feature?
Many of my items already have asset number labels on them. These asset numbers are a 6 digit hexadecimal string, not a number. It is not possible to use these in the asset ID field as the item then fails to save.
It would be nice to not have to use a custom field to store this data.
What is the solution you are proposing?
Allow non-numeric asset IDs.
What alternatives have you considered?
Custom field, which is clunky to say the least.
Additional context
No response
Contributions
I have searched through existing issues and feature requests to see if my idea has already been proposed.
If this feature is accepted, I would be willing to help implement and maintain this feature.
If this feature is accepted, I'm willing to sponsor the development of this feature.
The text was updated successfully, but these errors were encountered:
We have discussed this internally and will not be supporting this at this moment whilst we focus on more pressing issues.
We would advise usage of the API to re-print labels using the relevant IDs and leveraging search (which we have an epic for improved search).
What is the problem you are trying to solve with this feature?
Many of my items already have asset number labels on them. These asset numbers are a 6 digit hexadecimal string, not a number. It is not possible to use these in the asset ID field as the item then fails to save.
It would be nice to not have to use a custom field to store this data.
What is the solution you are proposing?
Allow non-numeric asset IDs.
What alternatives have you considered?
Custom field, which is clunky to say the least.
Additional context
No response
Contributions
The text was updated successfully, but these errors were encountered: