Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'retired' status #62

Closed
peelman opened this issue Nov 26, 2013 · 4 comments
Closed

Add 'retired' status #62

peelman opened this issue Nov 26, 2013 · 4 comments
Assignees
Labels
Milestone

Comments

@peelman
Copy link

peelman commented Nov 26, 2013

for the old stuff that goes away but you want to remember what it was and where it went...

might help if this could have a date attached to it somehow...

@snipe
Copy link
Owner

snipe commented Nov 26, 2013

You could use "Retired" as a status label right now - but funnily, I do already have an 'archived' boolean field on the assets table. I just haven't hooked anything into it yet.

@ghost ghost assigned snipe Nov 26, 2013
@peelman
Copy link
Author

peelman commented Nov 26, 2013

I recognize that, but I meant into the default set.

One could also go one step further and add "sold", "destroyed", but those are probably best left to the admin's discretion. There's a case to be made for "missing" too, as stolen implies theft, which is not always the case when things disappear, but again, that can always go at the user's discretion. "Retired" seems standard enough; when something is "archived" its status could automatically get set to retired. I'd say this could auto-set a date field too for retired/destroyed/etc but rarely would that ever be true. Things typically end up on the junk heap and then all get shuttled out at once; that's a tricky thing to try to track the date on, but definitely something worth keeping track of. knowing who disposed of something, when, why, and how are pretty important aspects for an asset tracker :)

@snipe
Copy link
Owner

snipe commented Nov 26, 2013

Of course, and dedending on how I handle that from a DB and UX perspective, it will either be a reserved status set (probably not), or a checkmark that marks it as retired and then adds a log entry about who/when/etc, same as checkouts and checkins do

@peelman
Copy link
Author

peelman commented Nov 26, 2013

Yeah, you have a nice framework for those kinds of timestamps, might as well reuse it.

@snipe snipe closed this as completed Feb 7, 2015
@snipe snipe removed the 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick! label Feb 7, 2015
This was referenced Jul 19, 2016
@bunzladi bunzladi mentioned this issue Mar 10, 2022
2 tasks
@Bjufen Bjufen mentioned this issue Feb 9, 2023
2 tasks
@manhvt20 manhvt20 mentioned this issue Mar 18, 2024
2 tasks
@uglycrab uglycrab mentioned this issue Mar 27, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants