Documenting Inter-Carrier Connections / Traces

[MrDragon]

I ran into a problem when trying to enter an inter carrier cross-connect between two different provider's circuits - running NetBox 3.4.4. Our data centers have provider cages/racks, and sometimes circuits / connections are made between providers - we provide the cross-connect/cable (and bill for it).

I tried to model this as follows:
Provider A Network <--> Circuit A-111 <-->
Panel-A1 rear-port 1 - Panel-A1, front-port 1 <--->
Panel-B1 front-port 1 Panel-B1 rear-port 1 <-->
Circuit B-222 <---> Provider B Network

That's how "reality" looks like, and yes, I can enter all this in NetBox. However, I cannot trace the cables. I've read through the docs, and it appears that the "gotcha" is that there's not a single interface in the entire mix.

I came across #10635, where the solution was to build bridged interfaces. I'll try to use that as a work-around (essentially replacing front/rear ports with "interface Front-1 / interface Rear-1, bridged"), but I wonder if there isn't a better way to do this.

I did build bridges, now I'm running into the issue described in #9076, where "everything depends on where you start the trace, but you'll never get a full end-to-end trace".

Any ideas would be appreciated.

I'll gladly submit that as a request, but I don't even know if I found a bug, if it's working-as-intended, or if it'd be a feature request.