Stroke start and end shapes

There is no easy way to copy/paste a line start and end shape when you copy/paste properties between lines in Figma. I use this for creating flow arrows between screens, but it only copies the color, dash/solid, and stroke width. It would be great to include the stroke start and end shapes with these properties so that I didn’t have to set these manually each time I draw a flow arrow.

Hey Moore, thank you for reaching out! I am not sure I follow, do you want the line to have a default option for the start/end point? Also, could you please clarify which properties you mean here? “copy/paste properties between lines”

Thank you,
Gayani

Sure thing, when I right click a line, where I have set the following properties for it’s stroke:

  • Color
  • Width
  • Dash
  • Circle arrow (at end)
  • Line arrow (at end)

Then, I right-click and select “copy properties”
Then, a go to another line I have drawn, with none of the above properties set (or using the default properties 1px black solid, no arrows on end), and right-click and select "paste properties,

The following properties/settings are NOT copied over to the new line:

  • Circle arrow (at end)
  • Line arrow (at end)

However, the width, color, dash properties are. I would like for the start and end arrows to copy over, as these are also properties that I’d like to reuse.

If you have multiple arrows you are drawing to link flows, Figma currently forces you to either copy/paste the line itself (which may or may not have the number of bends, connections, etc. that I need).

Thanks for clarifying @Moore_Cale! I tried to reproduce this on my end and the width property did not paste as well. I totally understand that this is a time consuming process to adjust the properties.

Let me share this internally with the team, because I am not sure if this is an intended behaviour. I’ll give you an update soon, appreciate your patience.

1 Like

Hey @Moore_Cale, apologies for the delayed response! The team has confirmed that this is unfortunately a long standing bug that our engineering team has been investigating. I’ve forwarded your post to the teams to take a look at.
To be transparent, it is likely not be prioritised in the long term due to the relatively easy manual fix for users.
However, please be assured that our team will continue to monitor the issue and I will reach out to you once we have any further updates.

Thank you,
Gayani