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

permission group changes skip the changelong #7505

New Issue
Closed
opened 2025-12-29 20:24:27 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:24:27 +01:00
Owner
Copy Link

Originally created by @mkurjanski on GitHub (Jan 13, 2023).

NetBox version

v3.3.9

Python version

3.8

Steps to Reproduce

  1. Go to the admin view => user permissions
  2. Add a new group to an existing permission profile (or create new profile if none available)
  3. The group assignment change does not get logged into the changelog

Expected Behavior

Whenever new group is assigned, removed or modified we should get the changelog entry.

Observed Behavior

No changelog entry observed.

Originally created by @mkurjanski on GitHub (Jan 13, 2023). ### NetBox version v3.3.9 ### Python version 3.8 ### Steps to Reproduce 1. Go to the admin view => user permissions 2. Add a new group to an existing permission profile (or create new profile if none available) 3. The group assignment change does not get logged into the changelog ### Expected Behavior Whenever new group is assigned, removed or modified we should get the changelog entry. ### Observed Behavior No changelog entry observed.
adam closed this issue 2025-12-29 20:24:27 +01:00
adam commented 2025-12-29 20:24:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 13, 2023):

The change log is intended to record changes to data within NetBox, rather than data about NetBox itself. I'm not sure it would make sense to extend the scope of the change log to cover users and permissions, but you're welcome to open a feature request citing your use case.

@jeremystretch commented on GitHub (Jan 13, 2023): The change log is intended to record changes to data within NetBox, rather than data about NetBox itself. I'm not sure it would make sense to extend the scope of the change log to cover users and permissions, but you're welcome to open a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) citing your use case.
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#7505
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?