add support of custom fields for Regions #780

Closed
opened 2025-12-29 16:25:44 +01:00 by adam · 3 comments
Owner

Originally created by @askbow on GitHub (Mar 20, 2017).

Issue type: feature request

Regions ( #164 ) are a very neat way of grouping sites, but they currently lack any informational fields beyond Name and nesting.
I think that adding Custom field capability to Regions would cover for most needs in that respect.

For example, some users might want to store Time Zone where the Region operates, or some other information (characterizing how hard it is to reach the region, for instance: regular, mountainous, polar, undersea, orbital, asteroid belt, gamma quadrant, etc).

Originally created by @askbow on GitHub (Mar 20, 2017). ### Issue type: feature request Regions ( #164 ) are a very neat way of grouping sites, but they currently lack any informational fields beyond Name and nesting. I think that adding Custom field capability to Regions would cover for most needs in that respect. For example, some users might want to store Time Zone where the Region operates, or some other information (_characterizing how hard it is to reach the region, for instance: regular, mountainous, polar, undersea, orbital, asteroid belt, gamma quadrant, etc_).
adam closed this issue 2025-12-29 16:25:44 +01:00
Author
Owner

@jeremystretch commented on GitHub (Mar 20, 2017):

Regions are secondary objects similar to rack groups and VLAN groups, which are used solely for the organization of primary objects. They aren't intended to store additional information. Rather, that information should be applies to sites directly.

@jeremystretch commented on GitHub (Mar 20, 2017): Regions are secondary objects similar to rack groups and VLAN groups, which are used solely for the organization of primary objects. They aren't intended to store additional information. Rather, that information should be applies to sites directly.
Author
Owner

@askbow commented on GitHub (Mar 20, 2017):

@jeremystretch I agree.
I had an idea and decided to open an "issue" about it, so it won't be lost.

Adding this feature might also result in duplicate and/or conflicting information down the road.

@askbow commented on GitHub (Mar 20, 2017): @jeremystretch I agree. I had an idea and decided to open an "issue" about it, so it won't be lost. Adding this feature might also result in duplicate and/or conflicting information down the road.
Author
Owner

@jeremystretch commented on GitHub (Mar 21, 2017):

Ok, cool. I'm going to close this out then.

@jeremystretch commented on GitHub (Mar 21, 2017): Ok, cool. I'm going to close this out then.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#780