Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to "watch" an object and be alerted to changes #15621

Closed
jeremystretch opened this issue Apr 4, 2024 · 0 comments
Closed

Ability to "watch" an object and be alerted to changes #15621

jeremystretch opened this issue Apr 4, 2024 · 0 comments
Assignees
@jeremystretch
Labels
complexity: high Expected to require a large amont of time and effort to implement relative to other tasks status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone
v4.1

Comments

@jeremystretch
Copy link
Member

NetBox version

v3.7.4

Feature type

New functionality

Proposed functionality

Provide the ability for a user to designate specific objects and receive notifications of any changes to those objects. Users should see a notification icon in the top right corner of the page when a new notification is present.

The notifications mechanism could piggyback off of the change log. Users should be able to designate specific objects as well as defining rules to match discrete sets of objects (e.g. "all devices in site A with role B").

Use case

Users may often desire to be alerted to specific types of changes in NetBox, such as when preparing for planned work or when informed of an ongoing issue.

Database changes

A new model would likely be required to define notification rules and associate them with a particular user (or group?). The rule format would likely mimic the one used to define permission constraints.

External dependencies

N/A
@jeremystretch jeremystretch added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Apr 4, 2024
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Apr 22, 2024
@jeremystretch jeremystretch added status: backlog Awaiting selection for work complexity: high Expected to require a large amont of time and effort to implement relative to other tasks labels May 21, 2024
@jeffgdotorg jeffgdotorg added this to the v4.1 milestone May 31, 2024
@jeffgdotorg jeffgdotorg removed the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Jun 7, 2024
@jeremystretch jeremystretch self-assigned this Jul 1, 2024
jeremystretch added a commit that referenced this issue Jul 3, 2024
@jeremystretch
Initial work on #15621
865619b
@jeremystretch jeremystretch mentioned this issue Jul 3, 2024
Merged
@jeremystretch jeremystretch mentioned this issue Jul 11, 2024
Closed
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: backlog Awaiting selection for work labels Jul 15, 2024
jeremystretch added a commit that referenced this issue Jul 15, 2024
@jeremystretch
Closes #15621: User notifications (#16800)
b0e7294 
* Initial work on #15621

* Signal receiver should ignore models which don't support notifications

* Flesh out NotificationGroup functionality

* Add NotificationGroup filters for users & groups

* Separate read & dimiss actions

* Enable one-click dismissals from notifications list

* Include total notification count in dropdown

* Drop 'kind' field from Notification model

* Register event types in the registry; add colors & icons

* Enable event rules to target notification groups

* Define dynamic choices for Notification.event_name

* Move event registration to core

* Add more job events

* Misc cleanup

* Misc cleanup

* Correct absolute URLs for notifications & subscriptions

* Optimize subscriber notifications

* Use core event types when queuing events

* Standardize queued event attribute to event_type; change content_type to object_type

* Rename Notification.event_name to event_type

* Restore NotificationGroupBulkEditView

* Add API tests

* Add view & filterset tests

* Add model documentation

* Fix tests

* Update notification bell when notifications have been cleared

* Ensure subscribe button appears only on relevant models

* Notifications/subscriptions cannot be ordered by object

* Misc cleanup

* Add event icon & type to notifications table

* Adjust icon sizing

* Mute color of read notifications

* Misc cleanup
jeremystretch added a commit that referenced this issue Jul 31, 2024
@jeremystretch
#15621: Add feature documentation for user notifications
5cfa2bb
jeremystretch added a commit that referenced this issue Aug 2, 2024
@jeremystretch
#15621: Support notifications for deletion of a subscribed object
57fe207
@jeremystretch jeremystretch mentioned this issue Sep 3, 2024
Merged
@jeremystretch jeremystretch mentioned this issue Sep 25, 2024
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
complexity: high Expected to require a large amont of time and effort to implement relative to other tasks status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
v4.1
Development

No branches or pull requests
2 participants
@jeffgdotorg @jeremystretch