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

Pre-populate "Date added" field or default date when adding aggregates #171

New Issue
Closed
opened 2025-12-29 15:35:43 +01:00 by adam · 4 comments
adam commented 2025-12-29 15:35:43 +01:00
Owner
Copy Link

Originally created by @bellwood on GitHub (Jul 7, 2016).

It looks like something changed since last week in respect to dates for added aggregates.

When I added these last week, the date defaulted to the current date.

I added a new aggregate today, left the field blank and it did not use todays date as the default.

Regression?

Originally created by @bellwood on GitHub (Jul 7, 2016). It looks like something changed since last week in respect to dates for added aggregates. When I added these last week, the date defaulted to the current date. I added a new aggregate today, left the field blank and it did not use todays date as the default. Regression?
adam closed this issue 2025-12-29 15:35:43 +01:00
adam commented 2025-12-29 15:35:43 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 7, 2016):

It appears there is a created date though?

@bellwood commented on GitHub (Jul 7, 2016): It appears there is a created date though?
adam commented 2025-12-29 15:35:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 7, 2016):

Ah, I can see the confusion. A while back we added created and last_updated fields to all of the core models, including Aggregate. These are simply to track the time of creation and most modification, respectively, of the record itself within NetBox.

Aggregate also happens to have a date_added field, which is meant to denote when the prefix it represents was allocated. It should probably be renamed to allocated_date or something similar. (This field is optional has never been auto-populated.)

@jeremystretch commented on GitHub (Jul 7, 2016): Ah, I can see the confusion. A while back we added `created` and `last_updated` fields to all of the core models, including Aggregate. These are simply to track the time of creation and most modification, respectively, of the record itself within NetBox. Aggregate also happens to have a `date_added` field, which is meant to denote when the prefix it represents was allocated. It should probably be renamed to `allocated_date` or something similar. (This field is optional has never been auto-populated.)
adam commented 2025-12-29 15:35:44 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 7, 2016):

Very weird, all my other aggregates have a "added" value in the table when viewing all my aggregates - none of which I entered on creation

/me shrugs

@bellwood commented on GitHub (Jul 7, 2016): Very weird, all my other aggregates have a "added" value in the table when viewing all my aggregates - none of which I entered on creation /me shrugs
adam commented 2025-12-29 15:35:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 7, 2016):

After some thought I'd rather not pre-populate this field, since the actual date of allocation or assignment is unlikely to be the same day it's created in NetBox.

@jeremystretch commented on GitHub (Jul 7, 2016): After some thought I'd rather not pre-populate this field, since the actual date of allocation or assignment is unlikely to be the same day it's created in NetBox.
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
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#171
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?