starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Make new custom Tag model a Changelog model #2407

New Issue
Closed
opened 2025-12-29 17:25:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:25:49 +01:00
Owner
Copy Link

Originally created by @lampwins on GitHub (Feb 22, 2019).

Originally assigned to: @lampwins on GitHub.

Environment

  • Python version: 3.7
  • NetBox version: develop-2.6

Proposed Functionality

In 2.6, NetBox migrates to use its own custom Tag model in place of the vanilla taggit model. In line with this change, the new Tag model should be made to be a Changelog model.

Use Case

Most all models in NetBox carry with them a changelog and since we now control the Tag model, this addition is trivial.

Database Changes

Tag will subclass ChangeLoggedModel and thus gain created and last_updated fields.

External Dependencies

None

Originally created by @lampwins on GitHub (Feb 22, 2019). Originally assigned to: @lampwins on GitHub. <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7 * NetBox version: develop-2.6 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality In 2.6, NetBox migrates to use its own custom `Tag` model in place of the vanilla taggit model. In line with this change, the new Tag model should be made to be a Changelog model. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Most all models in NetBox carry with them a changelog and since we now control the Tag model, this addition is trivial. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes `Tag` will subclass `ChangeLoggedModel` and thus gain `created` and `last_updated` fields. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 17:25:49 +01:00
adam closed this issue 2025-12-29 17:25:49 +01:00
adam commented 2025-12-29 17:25:49 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Feb 22, 2019):

Implemented in the develop-2.6 branch.

@lampwins commented on GitHub (Feb 22, 2019): Implemented in the develop-2.6 branch.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2407
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?