You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Nelly the Network Engineer, I want to be able to bulk edit the software version, which is a relationship from the DLM plugin, for a set of devices, so that I don't have to follow an unintuitive flow of going through the software model to change a device's software.
Use Case
Like #1317 and #1316 relationships are lacking several features that the average user would expect, given consistency in other areas.
This would likely not take advantage of #1593 once it is implemented due to the bulk nature of the modification.
Database Changes
We might need to look more deeply at the relationship model to support this.
External Dependencies
None
The text was updated successfully, but these errors were encountered:
Conceptually it seems like this would only make sense to include for many-to-many and many-to-one relationships (i.e. relationships where it's permissible for many different source objects to associate to the same destination object). I suppose for one-to-many and one-to-one relationships we could at least include a "delete" or "set null" checkbox though to allow bulk clearing of such a relationship?
Environment
Proposed Functionality
As Nelly the Network Engineer, I want to be able to bulk edit the software version, which is a relationship from the DLM plugin, for a set of devices, so that I don't have to follow an unintuitive flow of going through the software model to change a device's software.
Use Case
Like #1317 and #1316 relationships are lacking several features that the average user would expect, given consistency in other areas.
This would likely not take advantage of #1593 once it is implemented due to the bulk nature of the modification.
Database Changes
We might need to look more deeply at the relationship model to support this.
External Dependencies
None
The text was updated successfully, but these errors were encountered: