Standardize attributes and views for all primary models #3513

Closed
opened 2025-12-29 18:29:35 +01:00 by adam · 3 comments
Owner

Originally created by @jeremystretch on GitHub (Mar 27, 2020).

Proposed Changes

Standardize common attributes and views for all primary models. This work has been underway sporadically for the past few months, but needs to be formalized.

Justification

Establishes consistency for all models, and simplifies development and testing.

Originally created by @jeremystretch on GitHub (Mar 27, 2020). ### Proposed Changes Standardize common attributes and views for all [primary models](https://docs.google.com/spreadsheets/d/1UFoJHwCvpmPqTN6ARS977NFB5BLDvBiKlyIvlZpvUcg/edit#gid=0). This work has been underway sporadically for the past few months, but needs to be formalized. ### Justification Establishes consistency for all models, and simplifies development and testing.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 18:29:35 +01:00
adam closed this issue 2025-12-29 18:29:35 +01:00
Author
Owner

@xkilian commented on GitHub (Jun 11, 2020):

Has the normalisation process considered adding the Status attribute for a cable? I saw that custom fields where flagged as missing and aimed to be normalised, but there was no indication for Status. I can open an issue if this was not already planned.

@xkilian commented on GitHub (Jun 11, 2020): Has the normalisation process considered adding the Status attribute for a cable? I saw that custom fields where flagged as missing and aimed to be normalised, but there was no indication for Status. I can open an issue if this was not already planned.
Author
Owner

@jeremystretch commented on GitHub (Jun 11, 2020):

@xkilian Off-topic for this issue.

@jeremystretch commented on GitHub (Jun 11, 2020): @xkilian Off-topic for this issue.
Author
Owner

@jeremystretch commented on GitHub (Jul 2, 2020):

I'm going to consider this issue closed at this point. There remains a lot of work to be done around different models, however it's not practical to continue tracking it all under a single issue. This may be a good use case for GitHub projects.

@jeremystretch commented on GitHub (Jul 2, 2020): I'm going to consider this issue closed at this point. There remains a lot of work to be done around different models, however it's not practical to continue tracking it all under a single issue. This may be a good use case for GitHub projects.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3513