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

Reservation / booking system #541

New Issue
Closed
opened 2025-12-29 16:23:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:23:02 +01:00
Owner
Copy Link

Originally created by @nielipin on GitHub (Nov 18, 2016).

Hi,
thanks a lot for the great netbox !
One of the features I would like to see and I hope not only me ;) is some kind of booking calendar.
At the moment I am manually assigning devices to tenants and this method works fine, but I have to use some external calendar to plan in advance all activities.
I think I've seen a similar request some time ago but now I am not able to find it and check the status.
So I will kingly ask again, is there any plan to implement such feature in nearest future ?
thanks & regards,
Maciek

Originally created by @nielipin on GitHub (Nov 18, 2016). Hi, thanks a lot for the great netbox ! One of the features I would like to see and I hope not only me ;) is some kind of booking calendar. At the moment I am manually assigning devices to tenants and this method works fine, but I have to use some external calendar to plan in advance all activities. I think I've seen a similar request some time ago but now I am not able to find it and check the status. So I will kingly ask again, is there any plan to implement such feature in nearest future ? thanks & regards, Maciek
adam closed this issue 2025-12-29 16:23:02 +01:00
adam commented 2025-12-29 16:23:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 18, 2016):

I'm afraid this isn't actionable as a feature request. Per the contributing guidelines:

Good feature requests are very narrowly defined. Be sure to enumerate specific functionality and data schema. The more effort you put into writing a feature request, the better its chances are of being implemented. Overly broad feature requests will be closed.

@jeremystretch commented on GitHub (Nov 18, 2016): I'm afraid this isn't actionable as a feature request. Per the contributing guidelines: > Good feature requests are very narrowly defined. Be sure to enumerate specific functionality and data schema. The more effort you put into writing a feature request, the better its chances are of being implemented. Overly broad feature requests will be closed.
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
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#541
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?