Link cards together

Link these two cards so anyone on the project can navigate between the feature request and the related bug: 'Mobile nav redesign' and 'iOS nav overlap bug'. Add the link on both cards and write a one-line comment on each explaining the relationship and the current action owner. Set the relationship label to 'blocks' from the bug to the feature.

Before I link this feature card to three related bug cards, make the connection clear for a reviewer: show which card is blocking which, surface the evidence (screenshots or steps to reproduce) on the blocking card, and add a short note on how fix order affects release. Suggest precise wording for the link comment so a PM can triage quickly.

I just linked 'Mobile nav redesign' to 'iOS nav overlap bug' but developers think the feature work owns the fix and QA thinks the bug owner should. Given that both Alex (feature lead) and Priya (bug owner) are listed, how should ownership and next steps be assigned to avoid finger-pointing?

Across projects we create links without consistent verbs or context, and people misread them at standups. What naming convention and brief linking ritual can the team adopt so every link instantly shows who owns the next action and whether it blocks a release? Propose one clear rule and an example.