Circuit selection from a patchpanel not working

[lcioltan]

Environment

• Python version: Python 3.5.3
• NetBox version: Netbox 2.5.4

Steps to Reproduce

1. Use a version of a patchpanel with interfaces (let us name it "Patchpanel-A").
2. The rear port (Port-1) is connected to a distant patchpanel ("Patchpanel-B") via a carrier circuit ("Carrier-1"). The "Carrier-1" circuit has been defined in Netbox and it's listed under Circuits.
3. On the "Patchpanel-A" overview, under column "Connection", the distant "Patchpanel-B" is outputted and below it, with small letters, this circuit that connects the two panels (via "Carrier-1").
4. When you click on the circuit "Carrier-1", instead of being redirected to the circuit details,
   you land once again on the "Patchpanel-A"

Note: the problem doesn't appear with the front/rear ports patchpanels.

Expected Behavior

I expect to be redirected to the "Carrier-1" circuit.

Observed Behavior

I land on the exact same patchpanel (acts as a "refresh")

[jeremystretch]

Just use the "old" version of a patchpanel (with interfaces)

There is no "old" version of patch panels. Support for patch panels was introduced in v2.5. Please clarify what you mean.

[lcioltan]

Hi Jeremy,

I meant the patchpanel with interfaces (not with front/rear ports).

[jeremystretch]

Please edit your issue to include the exact steps that someone else can take to recreate the issue you're describing.

[lcioltan]

I just updated the description (Steps to reproduce).

[lcioltan]

[lcioltan]

Hi Jeremy,

I've attached a picture to better highlight the issue. If you need extra information, just let me know.

[jeremystretch]

I believe this was addressed under #2844 and will be fixed in v2.5.6. If you still have the issue on the new release, please ask for this to be reopened.

[lcioltan]

Hi Jeremy,

the issue persist after the v2.5.6 release. Can we re-open this ticket or should I create a new one?

Kind regards,
Lucian

[tvberlin]

@jeremystretch this is duplicated (and fixed now in 2.5.7) by #2914 and can now be closed, thanks.
@lcioltan FYI