Browse, vote, and track the status of feature requests from the NetBrain community
Browse open ideas available for voting, feedback, and discussion.
View ideas that are planned for future product development.
Explore ideas that are currently being developed by the product team.
Explore ideas that are now available in the product.
View ideas that are not currently planned for product development.
NetBrain currently does not allow users to filter neighbor devices by device type when a map is generated through an API-triggered diagnosis; all discovered neighbors are added to the map regardless of type. This enhancement would introduce a filtering option that lets users specify which device types to include or exclude from neighbor discovery during API-driven map creation. Customers running automated diagnostic workflows would be able to generate more focused and relevant maps, reducing manual cleanup and improving the efficiency of automated troubleshooting.
In the Runbook Compare feature, the 'Default Live' option is labeled in a way that suggests it will retrieve current live data, but it actually pulls only from data already present in the table and returns no results unless a separate retrieve action has been run first. This naming creates confusion, as users expect 'Default Live' to behave similarly to the 'Retrieve Data' action. This enhancement would rename the option to more accurately reflect its behavior, such as 'Temporary Data,' or remove it from contexts where it does not provide value. Clarifying this option would reduce user confusion and prevent customers from misinterpreting comparison results as reflecting live device data when they do not.
Dynamic Device Group search currently does not support filtering by Telnet/SSH login alias, Private CLI settings alias, or device access status (such as Fully Accessed via CLI or CLI Connection Failed). As a result, administrators cannot easily identify devices using non-standard credentials or connectivity states through dynamic search alone. This enhancement would add these three criteria as selectable options in the Dynamic Device Group search interface. Customers would be able to quickly identify credential mismatches across locations, target devices needing private CLI configuration, and group devices with access issues for operational follow-up without requiring access to the Data Accuracy Resolution table.
NetBrain's Change Management approval workflow currently supports only a single approver per change request, even when the underlying devices targeted by a Network Intent span multiple locations or organizational groups that each require sign-off from a different responsible person. This limits customers whose device approval requirements are defined per device or per group rather than uniformly across the change. This enhancement would allow either the generation of multiple change requests from a single Network Intent, each routed to the approver responsible for its associated devices, or the ability to request approval from more than one person on a single change request based on a defined device-approval mapping. Supporting flexible, device-aware approval routing would give organizations with distributed ownership stronger governance and reduce manual workarounds when applying the same change across multiple locations with different approvers.
NetBrain's REST API currently does not provide a method to programmatically trigger full execution of a Change Management task, Runbook, Network Intent, or QApp. Existing API capabilities support limited data retrieval scenarios but do not extend to initiating a complete change or automation workflow. This enhancement would introduce REST API endpoints that allow external systems to trigger execution of Change Management tasks, Runbooks, Network Intents, and QApps directly, supporting both change-module-governed and standalone runbook execution paths. Customers integrating NetBrain with ticketing, orchestration, or monitoring platforms would gain the ability to fully automate network change processes, such as device upgrades, without requiring manual initiation through the NetBrain user interface.
Within the Functional Portal Data View, tables such as MAC and NCT currently cannot be exported to CSV, and existing column resize and sort controls do not function as expected. In addition, devices placed on a large site map cannot be located using a Ctrl+F search, which limits efficient navigation. This enhancement proposes adding CSV export capability for Functional Portal Data View tables, restoring functional column resizing and sorting, and introducing a device search capability for large site maps. These improvements would allow customers to work more efficiently with large data sets and topology views, reducing manual effort when locating devices or extracting table data for offline analysis.
NetBrain currently restricts editing, disabling, or deleting a Change Analysis task to the user who originally created it. When that user is no longer part of the organization or is unavailable, no other user can manage the task through the application, requiring direct database access to remove or modify it. This enhancement would allow a user with System Admin rights to edit or delete any Change Analysis task regardless of who created it. This would give administrators a supported way to maintain task hygiene and continuity without relying on direct database intervention.
NetBrain does not currently retain the underlying command output within Network Intent results when the intent is executed in bulk or through a scheduled task, even though this output is available when the intent is run interactively on a single device. This enhancement would preserve and expose the command output associated with each device in bulk and scheduled Network Intent executions, consistent with prior product behavior. Retaining this data would allow operations teams to review the exact basis for diagnosis or troubleshooting outcomes after large-scale or unattended runs, rather than only seeing final results without supporting detail.
NetBrain currently does not allow an existing Change Management request to be edited once it has been created; any adjustment requires deleting the request and re-entering it from scratch, which discards the work already completed on that request. This enhancement would allow users to modify an in-progress Change Management request directly, preserving prior configuration and progress rather than requiring a full restart. Supporting in-place edits would reduce rework and save time for teams managing change requests that require adjustments after initial creation.
Today, when new devices are added through an ADT rebuild and new Network Intents are created, the commands required to benchmark those devices for Datasets must be submitted manually for each new device, creating ongoing administrative overhead as the network evolves. This enhancement would automatically submit the relevant benchmark commands for newly discovered devices, while still allowing an administrator to manually approve the submitted commands before they take effect. An alert or email notification when new commands are awaiting approval would keep administrators informed without requiring constant manual monitoring. This would make Datasets easier to maintain in environments where the network topology and device inventory change frequently.
NetBrain currently exports maps in a Visio format that fails to open correctly in other applications supporting the Visio file format, such as LibreOffice Draw, OpenOffice Draw, and draw.io. This enhancement proposes reviewing and adjusting the Visio export generation to align with the standard Visio file specification, ensuring broader compatibility across third-party tools. Customers who do not use Microsoft Visio internally rely on alternative Visio-compatible applications, and improved format compatibility would allow them to view and edit exported maps without errors.
The Shared Dashboards list currently displays only dashboards that have been placed inside a folder, dashboards that exist outside of any folder do not appear in the list at all. This enhancement would update the Shared Dashboards list to display all dashboards, whether or not they are organized into a folder. Customers would benefit from a complete and accurate view of their shared dashboards without needing to create additional folders solely to make existing dashboards visible.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.