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

Time zones should be user-settable #8500

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

Originally created by @pv2b on GitHub (Aug 23, 2023).

NetBox version

v3.5.8

Feature type

New functionality

Proposed functionality

The proposed functionality is a user-specific setting to set their preferred time zone for displaying the NetBox web UI.

Use case

In order to support teams that work in multiple timezones, it would be helpful if time zone display could be localized to a specific user.

It would also be useful for teams where some team members prefer having times displayed in UTC, and others prefer having them displayed in local time.

Database changes

There would need to be a field added to wherever the user preferences live, to allow for a timezone field.

External dependencies

No new dependencies should be needed. It appears that NetBox currently just passes TIME_ZONE down to Django anyway, and Django already provides functionality for user-specific timezones that could be leveraged by NetBox.

https://docs.djangoproject.com/en/4.2/topics/i18n/timezones/

Originally created by @pv2b on GitHub (Aug 23, 2023). ### NetBox version v3.5.8 ### Feature type New functionality ### Proposed functionality The proposed functionality is a user-specific setting to set their preferred time zone for displaying the NetBox web UI. ### Use case In order to support teams that work in multiple timezones, it would be helpful if time zone display could be localized to a specific user. It would also be useful for teams where some team members prefer having times displayed in UTC, and others prefer having them displayed in local time. ### Database changes There would need to be a field added to wherever the user preferences live, to allow for a timezone field. ### External dependencies No new dependencies should be needed. It appears that NetBox currently just passes TIME_ZONE down to Django anyway, and Django already provides functionality for user-specific timezones that could be leveraged by NetBox. https://docs.djangoproject.com/en/4.2/topics/i18n/timezones/
adam added the type: featurepending closure labels 2025-12-29 20:37:29 +01:00
adam closed this issue 2025-12-29 20:37:29 +01:00
adam commented 2025-12-29 20:37:30 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Aug 23, 2023):

As an side, it probably is a good way to have a way for the administrator to enable/disable this feature. Some organizations, for example, might have a mandate to always display times in a certain way (in UTC for example). A global toggle to enable/disable the feature might be a good idea.

@pv2b commented on GitHub (Aug 23, 2023): As an side, it probably is a good way to have a way for the administrator to enable/disable this feature. Some organizations, for example, might have a mandate to always display times in a certain way (in UTC for example). A global toggle to enable/disable the feature might be a good idea.
adam commented 2025-12-29 20:37:30 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Aug 23, 2023):

Ui changes would likely be needed to allow for setting a timezone on datetime fields (or at least notifying the user that their timezone is different from "default" timezone set in netbox and to account for any difference).

@ITJamie commented on GitHub (Aug 23, 2023): Ui changes would likely be needed to allow for setting a timezone on datetime fields (or at least notifying the user that their timezone is different from "default" timezone set in netbox and to account for any difference).
adam commented 2025-12-29 20:37:30 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Aug 23, 2023):

Ui changes would likely be needed to allow for setting a timezone on datetime fields (or at least notifying the user that their timezone is different from "default" timezone set in netbox and to account for any difference).

That's probably a good idea, even seperate from user-specific timezones being implemented. The UI isn't always very clear in telling the user what timezone is set in Netbox, often the only way to see is to scroll down to the bottom of the page and look at the tiny text down there.

@pv2b commented on GitHub (Aug 23, 2023): > Ui changes would likely be needed to allow for setting a timezone on datetime fields (or at least notifying the user that their timezone is different from "default" timezone set in netbox and to account for any difference). That's probably a good idea, even seperate from user-specific timezones being implemented. The UI isn't always very clear in telling the user what timezone is set in Netbox, often the only way to see is to scroll down to the bottom of the page and look at the tiny text down there.
adam commented 2025-12-29 20:37:30 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Aug 23, 2023):

The UI isn't always very clear in telling the user what timezone is set in Netbox

This is on every page at the bottom right side

image

@abhi1693 commented on GitHub (Aug 23, 2023): > The UI isn't always very clear in telling the user what timezone is set in Netbox This is on every page at the bottom right side ![image](https://github.com/netbox-community/netbox/assets/5083532/54d0650a-c7e7-4e7e-844c-7078a3269c0b)
adam commented 2025-12-29 20:37:31 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Aug 24, 2023):

The UI isn't always very clear in telling the user what timezone is set in Netbox

This is on every page at the bottom right side

image

Thank you for proving my point. Users often won't notice stuff at the very end, or at the bottom of the page, or fine print.

For example, in the post you just quoted, right after the piece you cut off (and I assume didn't notice because it was there at the very end), I wrote:

often the only way to see is to scroll down to the bottom of the page and look at the tiny text down there.

Which is essentially exactly what you just said.

@pv2b commented on GitHub (Aug 24, 2023): > > The UI isn't always very clear in telling the user what timezone is set in Netbox > > This is on every page at the bottom right side > > ![image](https://user-images.githubusercontent.com/5083532/262760798-54d0650a-c7e7-4e7e-844c-7078a3269c0b.png) Thank you for proving my point. Users often won't notice stuff at the very end, or at the bottom of the page, or fine print. For example, in the post you just quoted, right after the piece you cut off (and I assume didn't notice because it was there at the very end), I wrote: > often the only way to see is to scroll down to the bottom of the page and look at the tiny text down there. Which is essentially exactly what you just said.
adam commented 2025-12-29 20:37:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 23, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 23, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:37:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 23, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Dec 23, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#8500
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?