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 selects representative devices for test replication without regard to whether those devices are fully accessible, which can include devices with only partial connectivity such as SNMP-only or ping-only access. This limits confidence in replication outcomes, since a failure or inconsistency may stem from incomplete device access rather than the model or intent being tested. This enhancement would allow the representative device selection process for test replication to consider only devices that are fully accessible to NetBrain, such as those with confirmed CLI or API access. Customers would gain greater confidence that replication results reflect the actual behavior of the network intent rather than being skewed by device access limitations, reducing troubleshooting effort and improving the reliability of automation testing.
NetBrain currently does not automatically populate MPLS cloud objects on a map when a device is dragged and dropped onto that map. Users must take additional manual steps to have the MPLS cloud object appear and connect correctly with the newly placed device. This enhancement would ensure that MPLS cloud objects are automatically detected and rendered on the map as part of the drag-and-drop workflow. Customers building or maintaining WAN topology maps would benefit from more accurate, complete topology visibility without extra manual configuration steps.
Runbook input fields currently present as small, single-line text boxes with a limited character capacity, which restricts the amount of detail a user can enter when populating fields for integrations, such as third-party change request systems that support longer text entries. This enhancement would enlarge the input field display to span multiple rows and increase the supported character limit to align with common third-party field capacities. Customers would gain the ability to enter detailed implementation plans, justifications, and other extended information directly within Runbook inputs without truncation or workaround.
Universal Dashboards currently cannot be exported to Word or any other document format, and they are not available as a selectable content type within the Content Template Manager. This enhancement proposes adding native export functionality for Universal Dashboards to Word, along with an option to include Universal Dashboards as a component when building new Word document templates through the Content Template Manager. Supporting these capabilities would streamline the documentation workflow for partners and end users, allowing dashboard insights to be incorporated directly into reports and templates without manual recreation.
Chatbot macros currently require input values to be fed through a single, uniform method across all macros in a bot, with no option to assign a different input source per individual macro. This enhancement would allow each macro within a chatbot to be independently configured with its own input source, such as manual entry for one macro and an external table feed (for example, an ADT-backed source) for another. Customers building chatbots that reference a mix of static and dynamically sourced values, such as IP, MAC, and location data, would be able to configure each macro according to how that data is actually maintained, reducing manual upkeep and improving the accuracy of automated responses.
Plugin Manager currently does not provide a shared folder option, which limits users to organizing plugins in personal or local locations only. This enhancement would introduce a shared folder within Plugin Manager, allowing multiple users to access, organize, and manage a common set of plugins in one place. Customers with distributed teams would benefit from improved plugin reuse and consistency, reducing duplicate effort and simplifying plugin governance across the organization.
When a change is created through the Remediation action within a Network Intent, the system does not use a map object that the user has already created and saved; instead, it relies on a different, unsaved map for change creation. This requires the user to separately save the map used during the change process, creating an inconsistent workflow. This enhancement would allow users to specify which existing map object should be used for change creation when a Remediation action is triggered from a Network Intent. Supporting this capability would reduce redundant map-saving steps and provide consistent, predictable behavior when generating changes from automated diagnostics.
When using an Automated Data Table as the source for candidate devices in Chat Bot, the dropdown menu currently displays all devices in the table regardless of whether each device has the relevant replicated Network Intent data. This means devices without the applicable replicated data still appear as selectable options, requiring manual verification before use. This enhancement would add a filter to the Chat Bot candidate device dropdown so that only devices with the required replicated Network Intent are shown. Customers using ADT-driven Chat Bot workflows would gain a more accurate device selection experience and reduce the risk of choosing devices that lack the necessary data for the intended automation task.
NetBrain currently renders the Bus icon on L2 and L3 maps using a fixed, non-configurable appearance, giving administrators no way to visually distinguish or customize how shared network segments are represented. This enhancement would allow administrators to select or configure an alternative icon for the Bus element on maps. Providing this flexibility would improve map readability and let customers align the visual representation of shared segments with their own diagramming conventions.
NetBrain currently does not provide a way to export Cisco ACI license consumption details, including which ports are consuming licenses. This enhancement would add an export capability for ACI license usage that lists port-level license consumption alongside existing license summary data. Customers managing ACI environments would benefit from improved visibility into license allocation, enabling more accurate license audits and capacity planning.
NetBrain currently rebuilds Automated Data Tables (ADTs) on every scheduled or triggered cycle, regardless of whether the underlying seed intent has actually changed, which consumes unnecessary processing time and system resources. This enhancement would introduce a change-detection mechanism that compares the current seed intent state against the prior state and initiates a full ADT rebuild only when a meaningful change is detected. This capability would reduce processing overhead and shorten rebuild cycles, particularly benefiting environments with large device inventories or frequent scheduled rebuild intervals.
NetBrain does not currently update a Path Browser task's status to Failed when the task process is terminated externally, such as through a system task manager. As a result, the task status may remain inaccurate or unclear, leaving no reliable indicator that the task did not complete successfully. This enhancement would detect external termination of a running Path Browser task and update its status to Failed accordingly. Accurate status reporting would give customers confidence in monitoring task outcomes and would reduce the need for manual verification when a task is unexpectedly stopped.
NetBrain currently does not allow administrators to disable notification or admin-level email alerts for a specific individual user while leaving that user's automatic update functionality intact. Email settings are managed in a way that does not separate notification preferences from update processing on a per-user basis. This enhancement would introduce a user-level setting that allows an administrator to disable notification and admin email alerts for a designated user account without impacting that user's automatic update process. This would give organizations greater flexibility to manage email preferences for specific roles, such as executive or admin-level users, without disrupting core system functionality.
NetBrain currently supports exporting Visio site maps to local or on-premise file locations, but does not provide an option to export directly to a Box cloud storage share path. This enhancement would add Box as a configurable destination for both manual and scheduled Visio site map export tasks. Customers who rely on Box for centralized document sharing would be able to automate distribution of network diagrams without manual file transfer steps.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.