Allow Type filter in changelog list view #2199

Closed
opened 2025-12-29 17:23:31 +01:00 by adam · 0 comments
Owner

Originally created by @a31amit on GitHub (Dec 11, 2018).

Environment

  • Python version: 3.6
  • NetBox version: 2.5

Proposed Functionality

Please allow "Type" as filter option in the changelog list view. Similar to User and Action drop-down list

Use Case

This will allow a web user to filter based on Type and Narrow down the list to find specific change related to particular Type such as to know with device or inventory item or may be iterface etc.

Database Changes

None

External Dependencies

None

Originally created by @a31amit on GitHub (Dec 11, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.5 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Please allow "Type" as filter option in the changelog list view. Similar to User and Action drop-down list <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case This will allow a web user to filter based on Type and Narrow down the list to find specific change related to particular Type such as to know with device or inventory item or may be iterface etc. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 17:23:31 +01:00
adam closed this issue 2025-12-29 17:23:31 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2199