How to Block Jira Work Items and Add Blocked By Links Between Issues, Ep...

A blocked work item in Jira is an issue that cannot move forward because something else must be completed first. It represents work that is stuck, waiting for another team, another task, an approval or missing information. When an item is blocked the delay affects planning, sprint progress and team flow, so it is important to make the dependency visible. Jira allows teams to do this by linking issues together, giving everyone a clear understanding of what is causing the holdup and who owns the next step.

To show that an issue is blocked, you create a link between the two work items. You open the issue that cannot continue and select the option to link it to another issue. Jira then asks you to choose a link type. If the issue is being blocked, you select the is blocked by link. If the issue is the one causing the blockage for another item, you choose the blocks link. For example, if Issue A must be finished before Issue B can begin, then A blocks B. Once this relationship is created it appears on both issues and becomes part of your workflow. This helps teams react more quickly because blocked work is easy to identify during standups, sprint reviews and backlog grooming sessions.

Jira supports several types of issue links because not every relationship is a blocker. The relates to link indicates two issues share context but do not depend on each other. These links are useful when items involve the same feature, environment or customer outcome and benefit from being reviewed together. This link type does not imply waiting or delay but helps maintain awareness between connected pieces of work.

Jira also offers clone links. Cloning creates a new issue based on an existing one. This is helpful when similar work needs to be repeated in another environment or for a different customer. The clone link shows the connection between the original and the new copy so the team understands where the work came from. Another link type is duplicate. This is used when two issues describe the same request or problem. In these cases one issue is closed as a duplicate and the other remains active. The duplicate link preserves the relationship and keeps the project clean.

By using these link types teams gain visibility into how work items relate to one another. Blocked items become easier to track and resolve. Duplicate items are cleaned up more quickly. Related items stay grouped in a meaningful way. Cloned tasks maintain a clear history. All of this supports faster collaboration and reduces confusion about which issues must be addressed first.

A blocked work item is not just a status problem but a signal that something in the process needs attention. When blockers are visible teams can adjust workloads, communicate with the right people or take corrective action to clear the path. Jira’s linking features allow teams to represent these dependencies accurately so that decision making becomes smoother and bottlenecks can be removed early. By understanding and using blocks, is blocked by, relates to, clone and duplicate links, teams build a system of clarity that helps their projects move forward with confidence.

Cameron McKenzie is an AWS Certified AI Practitioner,Machine Learning Engineer,Solutions Architect and author of many popular books in the software development and Cloud Computing space. His growing YouTube channel has well over 30,000 subscribers.