Legacy Asset Tracking
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We need to be able to track old asset tags for computers. When an asset is Refreshed/Breakfixed, essentially the tag is removed from our system and replaced with a new one. We need to be able to track back one device for this process. This should be tracked on the asset and not employee as assets can move to employees.
For example: Asset NH123456 was Refreshed this year for NI123456. If we look up NI123456 we would like to see NH123456 tracked in case the information is required at a later date. For now a workaround can be adding a note on the workstation.
Assets get refreshed roughly every 4 years. Once refreshed again, it will replace the asset tag and it move to legacy again.
This was discussed from project onset and was expected to be included in the first version. We are marking this priority as "preferred for version 1" to accelerate the release schedule of version 1.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.