Add service expiration date to circuit model

[thisisjme]

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.

Database changes

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

External dependencies

No response

[DanSheps]

Database changes

No response

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

A detailed implementation plan would also be nice.

[jeremystretch]

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 😄

[thisisjme]

@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.

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 😄

[luhaijiao]

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

[jeremystretch]

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

[github-actions]

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.

[ryanmerolle]

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)