Team Use cases with Links Hierarchy

Team Use cases with Links Hierarchy

 

🛠️ Example team use cases

 

Use Case

How Teams Leverage Links Hierarchy

Use Case

How Teams Leverage Links Hierarchy

Planning a release

View all issues linked under a feature/initiative; roll-up estimates

QA test coverage

Link test cases to requirements; visualize coverage in hierarchy

Dependency cleanup review

Use matrix view across JQL filters and manage or delete unused links

Stakeholder reporting

Generate Excel exports showing progress at each hierarchy level

Onboarding external vendors

Share filtered hierarchy views to ensure visibility on open and blocked stories

 

 

🧩 Use Case Scenarios by Team

 

 

1. Cross-Team Coordination & Planning

 

Pivot Table View

  • Group or nest issues by the “Team” field:

    You’ll see blocked-out dependencies grouped per team.

  • Teams can easily track when their work is depending on or blocking other teams at a glance.

Screenshot 2025-07-09 at 00.36.37 (1).png

Map View

  • Visualize dependencies between teams using arrows connecting team-assigned issues.

  • Instantly spot teams that are bottlenecks or waiting on external input.

Screenshot 2025-07-08 at 23.58.06 (1).png

 

2. Sprint-Level Dependency Analytics

Pivot Table

  • Set rows as Team, columns as Sprint.

  • Roll-up metrics like story points or estimate totals per team per sprint to understand capacity and risk.

Screenshot 2025-07-27 at 00.00.31.png

 

Time estimation by Sprints

  • Filter to show a specific sprint and group by Team (select saved filter by Team).

  • See inter-team and intra-team dependencies concentrated in that sprint.

image-20250726-213649.png

 

 

4. Resource Allocation & Risk Mitigation

Pivot Table

  • Teams with high incoming dependencies and blocked issues become obvious.

  • PMs can reallocate resources proactively or assist those teams.

Dependency Map

  • Show only blocked dependencies and group by Team.

  • Visualize which teams have dependencies that impact others, and plan resolution escalation.

Screenshot 2025-07-26 at 23.47.32.png

 

📊 Example Table Layouts

View

Rows

Columns

Metrics & Use

View

Rows

Columns

Metrics & Use

Pivot

Team

Sprint / Status

Counts, story points, time estimates per team per sprint

Pivot

Team

Dependent Team

Number of links between teams; map load & cross-team connectors

Map (Grouping)

Dependency Map grouped by Team

—

Graph of cross-team issue links: blockers, status, assignee

 

 

💡 Why “Team” Custom Field is Powerful

  • Transforms issue data into team-level insights—not just per issue.

  • Enhances the ability to roll up progress and identify bottlenecks at team granularity.

  • Enables both analytical views (Pivot) and graphical overviews (Map) to surface team coordination gaps or overloads.

 

 

🛠️ How to Set It Up

 

  1. Create / configure the “Team” custom field:

    Use a dropdown or user picker where each issue is assigned to a team.

  2. In the Dependency Table:

    • In Pivot View, set “Team” as grouping axis (by adding customfield into pivot table).

    • In Map View, choose Group by Team filter (for example use saved filter with customfield Team='Name' AND project='Name'.) TRace dependencies only from this saved filte). Apply JQL filters to focus per team or sprint, depending on what view you need.

 

 

✅ Real-World Scenario

 

Imagine Team A, Team B, and Team C working on a coordinated release:

  • Team A’s stories depend on Team B delivering a component.

  • Team C handles testing across all deliverables.

  • Pivot Table: Team A shows high incoming dependencies from Team B; Team C shows blocked stories.

  • Map View: Arrows show Team B → Team A → Team C chains.

    Blocked arrows highlighted detect delays.

 

This setup lets Product Owners and PMs:

  • Swiftly reassign tasks,

  • Escalate blocked work,

  • Assess team load and risk across sprints.

Use Dependency Map+Pivot, or Matrix for this cases

Screenshot 2025-08-11 at 20.05.42.png

 

🟩 Matrix View – Key Use Cases

 

✅ Cross-Functional Dependency Mapping

  • Teams define two JQL filters (e.g. “Frontend Stories” vs “Backend Tasks”) to compare related work items.

  • The Matrix visually highlights issue relationships between the two sets, helping teams see which frontend stories depend on backend deliverables. 

  • Teams can add, delete, or edit links directly on the matrix — great for synchronizing cross-team work. 

✅ QA & Test Coverage

 

  • One axis can show requirements; the other shows test cases.

  • The Matrix displays which requirements have coverage, and gaps appear instantly.

  • QA leads and project managers can add missing links right in the interface. Ideal for test traceability. 

 

✅ Simplified Review & Cleanup

  • Set filters like “Old Bugs” vs “Current Features”.

  • Use the Matrix to catch stale or unnecessary links between legacy and current work.

  • Teams can clean up unused dependencies before release handoffs.

 

Screenshot 2025-07-09 at 00.03.54 (1).png

 

🔖 Saved Filters – How They Empower Teams

✅ Reusable Focused Views

 

  • Teams can create JQL-based saved filters like “Team A pending dependencies” or “Sprint 25 blocked issues.”

  • These filters feed both the Matrix and Pivot views, enabling consistent and repeatable reporting. 

✅ Shared Reports & Dashboards

  • Filters can be shared across the team, ensuring everyone sees the same dataset—no need to rebuild queries.

  • Leverage saved filters in dashboards or gadgets (e.g. “Links Matrix View gadget”) to display team-specific dependency data in real time. 

Screenshot 2025-07-09 at 00.47.00 (1).png

 

✅ Role-Based Insights

  • PMs create filters for release-level tracking; QA teams use filters focused on test-related dependencies.

  • Saved filters help teams switch between contexts quickly without confusion or SQL work.

 

 

🛠️ Practical Examples by Role

Role

Matrix View Example

Saved Filter Use

Role

Matrix View Example

Saved Filter Use

Frontend & Backend Teams

Compare “Frontend Tasks in Sprint X” vs “Backend Components” to track dependencies visually

Save filters like those two and reuse them to regenerate matrix view each sprint

QA / Testing Teams

Map “Requirements” vs “Test Cases” to see missing coverage

Use a saved filter for requirements; reuse matrix view and export traceability report

PM / Release Managers

Filter team-defined “Feature A deliverables” vs “Blocking Issues”

Create filters per initiative to be shown in dashboards or exported later

Technical Leadership

High-level Matrix: “Team A issues” vs “Team B issues” to highlight cross-team impacts

Saved filters power both views for recurring portfolio syncs

 

✅ Summary

 

  • Matrix View visualises how two sets of issues interconnect — ideal for inter-team alignment, QA mapping, or link cleanup.

  • Saved Filters provide reusable, shared query sets that maintain consistency across Matrix and Pivot usage and live dashboards.

  • Combined, they empower effortless coordination, traceability, and cross-functional clarity.

 

 

BACKLOG by Teams:

 

Create Quick filter on your Board (for example team= ‘Testers’ AND project='Name') and track their Backlog for a particular project

Step 1. Create Quick filter on your board for team:

Screenshot 2025-07-28 at 12.22.48.png

Step 2. Apply Quick Filter to your board:

Screenshot 2025-07-28 at 12.24.34.png

Step 3. Switch to Backlog and open through board configuration menu - Board Tracking :

Screenshot 2025-07-28 at 12.17.09.png

Step 4. Track work items assignet to the Team on board backlog :

Screenshot 2025-07-28 at 12.18.33.png

 

 

 

Contact us in case of any questions support@marketplace.expert