Martin Venclovsky

@bryanculver as requested I am adding top 2 use cases. Lets start discussion about these two and if it will be implemented we surely can work on other use cases....

@bryanculver Depicting the cable connection as block is a bit intrusive, especially if it will display interconnection between more layers of devices. If it would be just a line with...

I have come across a Netbox plugin which seem to create nice graphs of device interconnections: https://github.com/mattieserver/netbox-topology-views Have you considered creating a version of this for Nautobot? This would be...

The thing that container as a status prevents from setting real status to the prefix is one problem. Second issue is that Nautobot can't properly determine the utilization of a...

Adding some export/import inconsistencies which are not specifically mentioned here but are problem for us. field "rack_number" in export has to be "rack" in import field "rack_face" in export has...

@lampwins the rack name should be displayed but it should not contain facility ID because it is already displayed below and because it makes the name too long and it...

@bryanculver after discussion with our installation team `Rack Group` and `Tenant ` are the only one we are interested in. One related question: what do you this about possibility for...

@glennmatthews Thanks for this update. Rack Elevatin currently displays above Racks only Name, Role and Facility ID. We need another parameters (rack_environment, number of phases in rack, Power, number of...

@lampwins Yes that would work but this would have to include custom fields as all the parameters we need to see are extra/custom parameters.