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

Site Timezone Selection #1043

New Issue
Closed
opened 2025-12-29 16:28:13 +01:00 by adam · 10 comments
adam commented 2025-12-29 16:28:13 +01:00
Owner
Copy Link

Originally created by @rsaturns on GitHub (Jun 16, 2017).

Issue type: Feature Request

When adding a site it would be nice to have a Timezone field that could be selected. This would then document the local Timezone for the site. Additionally if selected below it could display the sites current local time as calculated from the servers off-set.

For example, the server is set to PST and the time is 0700 and the date is June-16-2017. Site timezone is selected as EST.

The selection field shows:
US/Eastern
Below the selection field is actual time:
10:00 US/Eastern June-16-2017

Originally created by @rsaturns on GitHub (Jun 16, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Feature Request <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> When adding a site it would be nice to have a Timezone field that could be selected. This would then document the local Timezone for the site. Additionally if selected below it could display the sites current local time as calculated from the servers off-set. For example, the server is set to PST and the time is 0700 and the date is June-16-2017. Site timezone is selected as EST. The selection field shows: US/Eastern Below the selection field is actual time: 10:00 US/Eastern June-16-2017
adam added the type: feature label 2025-12-29 16:28:13 +01:00
adam closed this issue 2025-12-29 16:28:13 +01:00
adam commented 2025-12-29 16:28:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 16, 2017):

I like it, but we need to figure out how to cultivate a list of timezones for a user to choose from. Something like django-timezone-field should work, although it would introduce a new dependency, and I'm not sure how we'd maintain timezone choices over time.

@jeremystretch commented on GitHub (Jun 16, 2017): I like it, but we need to figure out how to cultivate a list of timezones for a user to choose from. Something like [django-timezone-field](https://github.com/mfogel/django-timezone-field) should work, although it would introduce a new dependency, and I'm not sure how we'd maintain timezone choices over time.
adam commented 2025-12-29 16:28:14 +01:00
Author
Owner
Copy Link

@rsaturns commented on GitHub (Jun 16, 2017):

What about if on the Django admin portal you exposed all the Timezones as tick boxes. Then as an admin, you select the ones you want to apply to you. In our case, as a global company we really only operate in about 14 timezones world wide. So I'd "tick" those 14 which would then be presented to me in the drop-down list on the add site front end?

@rsaturns commented on GitHub (Jun 16, 2017): What about if on the Django admin portal you exposed all the Timezones as tick boxes. Then as an admin, you select the ones you want to apply to you. In our case, as a global company we really only operate in about 14 timezones world wide. So I'd "tick" those 14 which would then be presented to me in the drop-down list on the add site front end?
adam commented 2025-12-29 16:28:14 +01:00
Author
Owner
Copy Link

@rkutsel commented on GitHub (Jun 17, 2017):

I'm might be totally off base here but what's wrong with setting it to UTC
which should be a gold standard for local times worldwide. I don't see any
practical use case here other than a convenience.

@rkutsel commented on GitHub (Jun 17, 2017): I'm might be totally off base here but what's wrong with setting it to UTC which should be a gold standard for local times worldwide. I don't see any practical use case here other than a convenience.
adam commented 2025-12-29 16:28:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 19, 2017):

I think the proposal is simply to track the local time for each site, so that it can be referenced in maintenance notices and whatnot.

@jeremystretch commented on GitHub (Jun 19, 2017): I think the proposal is simply to track the local time for each site, so that it can be referenced in maintenance notices and whatnot.
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@rsaturns commented on GitHub (Jun 19, 2017):

That is exactly correct. Nothing is more fun then to have an operations team do a page out to on-call only to find out it's for a site that is past business hours with no contacts.

@rsaturns commented on GitHub (Jun 19, 2017): That is exactly correct. Nothing is more fun then to have an operations team do a page out to on-call only to find out it's for a site that is past business hours with no contacts.
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@rkutsel commented on GitHub (Jun 19, 2017):

Makes sense. This feature will definitely come in handy.

@rkutsel commented on GitHub (Jun 19, 2017): Makes sense. This feature will definitely come in handy.
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@vsvetlov commented on GitHub (Nov 14, 2017):

It would be nice to add "maintenance window" field for a site model.
For example 11 PM - 6AM.

Can a current time field be highlighted with different colours if it is in or out of site's MW?

@vsvetlov commented on GitHub (Nov 14, 2017): It would be nice to add "maintenance window" field for a site model. For example 11 PM - 6AM. Can a current time field be highlighted with different colours if it is in or out of site's MW?
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 19, 2017):

Implemented in b20258c

@jeremystretch commented on GitHub (Dec 19, 2017): Implemented in b20258c
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@lmgonzalezl commented on GitHub (Jun 13, 2019):

Hi.

First, give thanks for the contribution you have made with Netbox.

We are implementing it in the company and we would like to change the TIME_ZONE in the configuration.py file to adjust it to our time use. We are in the Canary Islands - Spain and our time use is UTC +01: 00.
I have placed TIME_ZONe = 'UTP +01: 00' but it does not work. Can you tell me what is the correct way to assign this parameter?

Greetings and thank you.

@lmgonzalezl commented on GitHub (Jun 13, 2019): Hi. First, give thanks for the contribution you have made with Netbox. We are implementing it in the company and we would like to change the TIME_ZONE in the configuration.py file to adjust it to our time use. We are in the Canary Islands - Spain and our time use is UTC +01: 00. I have placed TIME_ZONe = 'UTP +01: 00' but it does not work. Can you tell me what is the correct way to assign this parameter? Greetings and thank you.
adam commented 2025-12-29 16:28:15 +01:00
Author
Owner
Copy Link

@lmgonzalezl commented on GitHub (Jun 17, 2019):

Resolved.

TIME_ZONE = "Atlantic/Canary"

Thank you.

@lmgonzalezl commented on GitHub (Jun 17, 2019): Resolved. TIME_ZONE = "Atlantic/Canary" Thank you.
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 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#1043
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?