Issue relationships and resolution notes

Choose the relationship direction

Limin models dependencies in two directions:

• Blocked by means the current issue is waiting for another issue.
• Blocking means the current issue is preventing another issue from progressing.

The relationship is shown on both issues. If APP-20 is blocked by API-8, then API-8 is shown as blocking APP-20.

Add an existing issue as a blocker

1. Open the issue that cannot progress.
2. Choose Add beside its relationships.
3. Select Blocked by.
4. Search by issue title or public ID.
5. Choose the blocking issue.

You can create the relationship from an issue card’s context menu as well. Limin prevents duplicate and self-referencing relationships.

If the required blocker does not exist yet, use the Create new issue action in the relationship search. The new issue is created with the relationship already attached.

Follow blocker updates

When a blocking issue receives resolution notes or is completed, the dependent issue shows those blocker updates in its own detail screen. This keeps the most useful outcome close to the work that was waiting for it.

Resolved blockers remain visible as context. Removing a relationship removes the connection, not either issue.

Write resolution notes

Resolution notes explain how the blocking issue was resolved. The field can be filled when an issue reaches an In progress or Done status, or whenever notes already exist.

Good resolution notes can include:

• The approach taken.
• A behaviour or constraint that changed.
• Technical specifications like a new API.
• A link to design files ready to be implemented.
• Anything a blocked teammate must know before continuing.

Resolution notes support the same formatting and issue mentions as descriptions and comments.

Relationships versus links and mentions

Use a blocking relationship when progress genuinely depends on another issue, or when you want its resolution notes to appear automatically in the dependent issue.

Use an issue mention for supporting context. Use Copy issue link when sharing the issue outside the editor.

This distinction keeps board blockers meaningful and prevents loosely related work from appearing as a dependency.