Linked Issue Dependency Mapper

🔹 Introduction

Welcome to the official documentation for Linked Issue Dependency Mapper, a Jira Cloud app developed by PgM Innovations.

In fast-moving teams, hidden dependencies often slow delivery, create misalignment, and blur ownership. While Jira lets you link issues, it doesn’t show the full picture — especially across projects.

Linked Issue Dependency Mapper fixes that by giving you:

• One view for all deliverables and blockers

• Multi-level dependency visibility without opening issues

• Inline commenting for instant follow-ups

• Cross-project impact detection to manage what’s at risk

• Proactive “Blocks” view to see where your team is blocking others

Whether you’re a Scrum Master, Project Manager, or Delivery Lead, this app helps you spot blockers early, act fast, and keep sprints on track.

🔹 Table of Contents

🔹 Key Concepts

In Jira, users can link issues using various relationship types. Among these, "Is Blocked By" and "Blocks" are particularly important for tracking dependencies:

Example: Refer to the screenshot of issue INTG-3, which Is Blocked By two tickets: DOPS-6 and PROD-5. This means that in order to deliver INTG-3, the team must first resolve or complete DOPS-6 and PROD-5. Only then can they work on INTG-3 and move forward.

Open

Similarly, if we access DOPS-6, we will get the below view, which highlights that DOPS-6 Blocks INTG-5

Open

🔹Getting Started

Once the app has been successfully installed by your Jira administrator, users can begin using the app by navigating through the following steps:

Click on Apps. Then click on 'Linked Issue Dependency Mapper'

Open

🔹Creating a Report

You can generate a report by:

1. Choose an existing Jira Saved Filter, or type a custom JQL query.

Open

or type a custom JQL query.

Open

2. Select the Linked Issue Type from the dropdown:

   1. Is Blocked By: Shows tickets blocked by others.

   2. Blocks: Shows tickets that are blocking others.

Open

Your report is ready to be viewed.

🔹Report Views

Is Blocked By View

• Shows deliverables along with their blocking tickets.

• Click on the "Blocked By" field to expand and view details of each blocker.

• Supports multi-level blockers. Example:

  • A → Blocked by B → Blocked by C → and so on.

When this option is selected, the report displays your primary deliverables alongside the tickets that are currently blocking them. This view helps you quickly identify what needs to be resolved before progressing with your own work. In this view, a user gets 2 checkboxes to further filter the result.

Only Show Blocked Tickets:

• Filters out tickets that do not have any associated blockers.

• For example, as demonstrated in the reference video, selecting this checkbox would remove tickets like DEMO-2 and DEMO-5 from the view, since they have no linked blockers.

Open

Only Show Actively Blocked Tickets:

• Hides tickets that either have no blockers linked to them or have blockers that are no longer in an active state (e.g., marked as Done, Closed, or Completed).

• As demonstrated in the reference video, selecting this checkbox would remove tickets such as DEMO-1, DEMO-2, and DEMO-5 from the view.

Open

Blocks View

• Shows your team’s tickets that are blocking other tickets.

• Replaces the "Blocked By" column with a "Blocks" column.

When this option is selected, the report generates a proactive view that highlights tickets from your project(s) that are currently blocking work for other individuals or teams. This enables project and product owners to identify dependencies they are responsible for clearing. In this view, a user gets 2 checkboxes to further filter the result.

Exclude Tickets Which Are Not Blocking Other Tickets:

• Filters out tickets from the selected filter or JQL query that are not blocking any other issues.

• As demonstrated in the reference video, selecting this checkbox will remove tickets such as DOPS-1 and DOPS-10 from the view, since they are not acting as blockers.

Open

Exclude Tickets Which Are Not Actively Blocking Other Tickets:

• Filters out tickets from the selected filter or JQL query that are not blocking any other tickets, as well as tickets that were previously blocking others but are now marked as Done, Closed, Released, or Completed (indicated by a green status).

• As demonstrated in the reference video, selecting this checkbox will remove tickets such as DOPS-1, DOPS-3, DOPS-4, and DOPS-10 from the view.

Open

🔹 Field Descriptions

Once you have selected the required parameters, the data will appear like below with the default columns.

Open

🔹 Column Management

• Default columns: Key, Summary, Assignee, Status, Due Date, Blocked By/Blocks, and Comment.

• Use the column icon to:

  • Add new columns or remove default columns.

  • Rearrange the column order.

Open

Search for a new column that needs to be added or uncheck a column that is not needed.

Open

Note: "Blocked By/Blocks" and "Comment" columns cannot be removed.

🔹 Reading the Data

To view detailed information about blocker or dependent tickets, simply click on the Blocked By or Blocks column next to any deliverable in your report. Upon clicking, the row expands to display metadata such as status, summary, assignee, and due date for each related ticket.

For example, in the referenced video, issue INTG-5 is blocked by PROD-3, DOPS-3, and PROD-6. When the user clicks the "Blocked By" column for INTG-5, the expanded row displays all relevant details of these three blockers.

This feature also supports multi-level dependency tracking. If PROD-6 is further blocked by PROD-4, clicking the "Blocked By" column next to PROD-6 will reveal PROD-4 and its information.

Open

NOTE: A ticket with a strike (PROD-2) denotes that the ticket is in complete (Done/Released/Closed) status.

You can expand multiple tickets simultaneously. To collapse a single expanded row, click on the same "Blocked By" or "Blocks" field again. To collapse all rows at once, use the Collapse All button at the top of the report. for any ticket to expand its details. This expanded view shows:

• All linked blocker or dependent tickets.

• Key metadata like status, summary, due date, and assignee for each blocker.

• Multi-level dependencies (e.g., Ticket A → blocked by B → blocked by C) are also visible in a cascading format.

Users can expand multiple rows at a time. To reset, simply click Collapse All to return to the default view.

Open

🔹 Commenting on Issues

• Click the comment icon in any row to open a pop-up window.

• You can leave a message or @mention a teammate to follow up on the primary deliverable or any of its blocker tickets.

• This allows users to engage directly with issue stakeholders without opening the ticket in a separate Jira window.

• For a demonstration, please refer to the video tutorial linked below.

Open

🔹 Saving and Accessing Reports

Saving:

• Use the Save button to preserve your configured report for future reference.

• After clicking save, you will be prompted to:

  • Enter a report name

  • Choose the visibility of the report:

    • Private: Only visible to you.

    • Public: Accessible to everyone in your Jira instance.

• For a step-by-step demonstration, please refer to the instructional video below.

Open

Accessing:

• All saved reports appear under the menu option 'Saved Reports'.

• Click to load any saved view.

🔹 Exporting Data

• Click Export to download the current report as an Excel file.

• Export respects column selection and filtering.

🔹 Links

• ❓Frequently Asked Questions

• 💡Feedback, Suggestions, or Queries, Click Here.

• ▶️ Detailed videos on the Linked Issue Dependency Mapper App, Click Here.

• 🌐Learn more about PgM Innovation, Click Here.

• 📥Install the app, Click Here.