View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|1087||RackTables||default||public||2013-11-23 17:16||2018-07-05 14:15|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Summary||1087: Archival of objects|
|Description||Sorry to reopen this|
you mentioned tagging will do, but the removed hardware cant be created ( reused ) again
1. mac-address shouldn't match as the decommsioned and reused will clash
2. only other way is to remove all ports, serial numbers and stuff
int this way there is no point to keep track of decommissioned object.
If I may only way is to move a copy of existing object to a new table and which has nothing but history.
|Tags||No tags attached.|
|related to||953||closed||andriyanov||Archival of objects|
|has duplicate||1493||closed||andriyanov||Add "active" attribute in table objects|
|has duplicate||1691||closed||Add option to archive devices when decomissioned|
|has duplicate||1829||closed||Keep deleted Objects in Database|
I'm not sure if I understand your use case right.
You just want to keep the name of an object along with its history to say "this object was here, but it is not available anymore" ?
At the same time you want to reuse the device name for a new object with differnt hardware?
Please specify your use case more.
yes this is to keep track of devices that have influenced the network and has been decommissioned.
it might be the same device might be reused in a different purpose with different entities
well you could do what you said in 2.)
after deleting ports and stuff you should be able to assign the unused tag. The log history - which keeps track of the state of the art - is still there.
I don't see any problem for a reuse of the hardware later. You must create an new object then but thats all.
yes but with out any serial/id how what use will it be to keep them
I think it would be better to have an option of move the decommissioned devices in a different way. but just to mention this is not high prioriy
when compared to
|2013-11-23 17:email@example.com||New Issue|
|2013-11-24 12:39||cyb3rwulf||Note Added: 0001969|
|2013-11-24 18:firstname.lastname@example.org||Note Added: 0001971|
|2013-11-25 01:17||cyb3rwulf||Note Added: 0001979|
|2013-11-25 15:email@example.com||Note Added: 0001981|
|2015-08-09 22:19||adoom42||Relationship added||related to 1493|
|2017-02-09 11:52||infrastation||Relationship added||has duplicate 1691|
|2017-02-09 11:54||infrastation||Relationship replaced||has duplicate 1493|
|2017-02-09 11:54||infrastation||Relationship added||related to 953|
|2018-07-05 14:15||infrastation||Relationship added||has duplicate 1829|