Mario

@renatoalmeidaoliveira To be honest I don't see any advantage in a modal window. It's very unflexible in many ways. I mean, what's the big deal to click the back button...

Removing the modal window would also Fix #611.

Choices in model IndividualOptions are hard coded in english. This leads to link.termination_type.name won't be found in supported_termination_types in views.py, because the name value represents the translated termination type. >views.py:...

Just had a closer look. We could use **link.termination_type.model** instead. Unfortunately we need to make changes to the model if we go this way. I don't get why **link.termination_type.name** is...

It's not a bug, it's a feature 😉 Thank you for reporting this bug. I was able to reproduce this behavior. It is not necessary to have all the options...

Personally I don't see why an export should be different from the view that is being exported. So, the proposal should rather be like "add port information to the connections...

Just to clarify: I created a mockup from a real calculation. This is what vis-network does when you put a label on every edge:   The best result I...

I've changed the title in order reflect the indended proposal. So, the following needs to be done in the export function: Get the connection information (like it can be seen...

Hi Brian, thank you for reporting this issue. I didn't even know that a non-login-mode exists. Individual options - as the name implies - store options for registered individuals (aka...

This may be a tricky one because the filter tab belongs to devices, not circuits. As circuits are a different data model, I'm not sure if we can handle this.