Lines that take you to destination

  • 9 December 2020
  • 5 replies
  • 361 views

Is there a way to make lines clickable so they take you to their connecting site? Trying to track the through line while zooming in and out is difficult.


5 replies

Userlevel 1

I would love a Link To capability in the connection line feature. I don’t necessarily want all connection lines to do this. But I definitely have a need to quickly string elements together w/o having to summon the contextual menu to select the Link To, and find what I want in a huge Miro board. 

 

We already have 4 kinds of connectors. The ability to somehow make them have the ability to Link To would really speed things up for me.

I was about to create the same idea, while @Robert Johnson makes a good point in that the “link to” feature does the same thing, it is limited to one connection per item.

However, if you had a sticky with has multiple connection lines, and lets say you had 2x connected items nearby but 2x connected items were on far off locations on the board, it would be handy to be able to click a select line and get transported along it like a little train or zip-line type effect that brings you to the connected item :-)

Improvements on this feature later on would perhaps be to have ability to adjust the speed at which you get transported from one side of the connection line to the other. It would look cool if the trigger was a arrow along the line, near the connected item, on other side, pointed toward the other direction.

Userlevel 7
Badge +12

@Echo - This ticket was still open with no updates. I presume the lack of “Link to” is intentional as linking to a connection line that is connected to one or more objects may be ambiguous as to what the user should be looking at once they follow the link.

Userlevel 7
Badge +12

Ticket submitted. I will report back here.

Userlevel 7
Badge +12

@Echo - There is the Link to option when you select a connection line on its own, but when it is connected to at least one object, the Link to option is missing. However, there is a workaround → use the Ctrl/Cmd + K shortcut:

 

I can see how this behaviour could be by design, but it could also be a bug. I will report this to Miro support for a definitive answer.

Reply