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

Add service expiration date to circuit model #5286

New Issue
Closed
opened 2025-12-29 19:26:12 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:26:12 +01:00
Owner
Copy Link

Originally created by @thisisjme on GitHub (Sep 1, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.10

Feature type

Change to existing functionality

Proposed functionality

Circuit Contract Management

The ability to add an expiry date / define contract length of a Circuit (bonus points) = display days to expiry.
Ability to put a notification for renewals - i.e. 90 day Notice Period

Use case

When users of NetBox visit or review a site they will have visibility of the circuit in full i.e. circuits that are nearing end of contract and need renewing or cancelling.

NetBox-FR

Database changes

New Field 'Expiry Date' - Date Value
Lookup 'Expiry Date' minus todays date.

External dependencies

No response

Originally created by @thisisjme on GitHub (Sep 1, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.10 ### Feature type Change to existing functionality ### Proposed functionality **Circuit Contract Management** The ability to add an expiry date / define contract length of a Circuit **(bonus points)** = display days to expiry. Ability to put a notification for renewals - i.e. 90 day Notice Period ### Use case When users of NetBox visit or review a site they will have visibility of the circuit in full i.e. circuits that are nearing end of contract and need renewing or cancelling. ![NetBox-FR](https://user-images.githubusercontent.com/89916008/131670622-769466bd-9ac8-4b90-b2a5-b6c3220dcc95.jpg) ### Database changes New Field 'Expiry Date' - Date Value Lookup 'Expiry Date' minus todays date. ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:26:13 +01:00
adam closed this issue 2025-12-29 19:26:13 +01:00
adam commented 2025-12-29 19:26:13 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 1, 2021):

Database changes

No response

Pretty sure you need something here, please update and resubmit.

A detailed implementation plan would also be nice.

@DanSheps commented on GitHub (Sep 1, 2021): > ### Database changes > _No response_ Pretty sure you need something here, please update and resubmit. A detailed implementation plan would also be nice.
adam commented 2025-12-29 19:26:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 1, 2021):

You also run into the very common issue of determining which two pieces of data to track in order to infer a third. Do you track start and end date to determine the total length, or start date and length to determine the end date?

10/10 on the screenshot though 😄

@jeremystretch commented on GitHub (Sep 1, 2021): You also run into the very common issue of determining which two pieces of data to track in order to infer a third. Do you track start and end date to determine the total length, or start date and length to determine the end date? 10/10 on the screenshot though :smile:
adam commented 2025-12-29 19:26:14 +01:00
Author
Owner
Copy Link

@thisisjme commented on GitHub (Sep 1, 2021):

@DanSheps my apologies, newbie here / will rectify asap.

@jeremystretch agreed! I/we have been previously tracking this kind of information in excel but are now in the process of documenting everything in NetBox.

Netbox-FR01

I would keep both the Start & Expiry dates as static date values but to get the third (days remaining) a lookup of the expiry date minus todays date.

10/10 on the screenshot though

MS Paint is life 😄

@thisisjme commented on GitHub (Sep 1, 2021): @DanSheps my apologies, newbie here / will rectify asap. @jeremystretch agreed! I/we have been previously tracking this kind of information in excel but are now in the process of documenting everything in NetBox. ![Netbox-FR01](https://user-images.githubusercontent.com/89916008/131691322-4b909a43-b0c6-4ebf-ad27-ec76760cfc8d.png) I would keep both the Start & Expiry dates as static date values but to get the third (days remaining) a lookup of the expiry date minus todays date. > 10/10 on the screenshot though MS Paint is life 😄
adam commented 2025-12-29 19:26:14 +01:00
Author
Owner
Copy Link

@luhaijiao commented on GitHub (Sep 10, 2021):

I would expect this kind of contract management for all devices if possible :-)

@luhaijiao commented on GitHub (Sep 10, 2021): I would expect this kind of contract management for all devices if possible :-)
adam commented 2025-12-29 19:26:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 10, 2021):

@luhaijiao that would require a separate FR as it's beyond the scope of the proposal here.

@jeremystretch commented on GitHub (Sep 10, 2021): @luhaijiao that would require a separate FR as it's beyond the scope of the proposal here.
adam commented 2025-12-29 19:26:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 10, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 10, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:26:14 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jan 14, 2022):

Not trying to pile into this request, but just throwing out some of my common fields for circuits. COuld be a good discussion for other possible FRs OR just nice for people to take inspiration from for their own custom fields.

Circuit Custom Fields I use:

  • Term End Date (basically this FR field)
  • Order Date
  • Order ID
  • Committed latency
  • Decommission Date (Disconnect Date either passed and status is decommissioned OR upcoming disconnec)
  • Current Term (useful if you renegotiated circuits - Would be a number of months 12, 24, 36 OR month-to-month)
  • Current Term Start date (useful if you renegotiated circuits)
  • MRC (Monthly reoccurring cost)
  • NRC (non-reoccurring cost / install fee)
@ryanmerolle commented on GitHub (Jan 14, 2022): Not trying to pile into this request, but just throwing out some of my common fields for circuits. COuld be a good discussion for other possible FRs OR just nice for people to take inspiration from for their own custom fields. Circuit Custom Fields I use: - Term End Date (basically this FR field) - Order Date - Order ID - Committed latency - Decommission Date (Disconnect Date either passed and status is decommissioned OR upcoming disconnec) - Current Term (useful if you renegotiated circuits - Would be a number of months 12, 24, 36 OR month-to-month) - Current Term Start date (useful if you renegotiated circuits) - MRC (Monthly reoccurring cost) - NRC (non-reoccurring cost / install fee)
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#5286
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?