Skip to main content
Skip table of contents

Dependency lines: issue links in on the User Story Map

This feature is currently only available for Easy Agile TeamRhythm on Jira Cloud.

When making plans, it’s important to understand the dependencies involved in the work. This allows you to prioritize and sequence your work so your team can execute the plans smoothly.

Dependencies can turn into blockers and bottlenecks that disrupt the team’s flow. By spotting and addressing them early, you can respond to problems and keep going.

Too many dependencies can also indicate a problem with how work is broken down. Easy Agile recommends the “INVEST” strategy to craft user stories which are independent.

On the User Story Map, you can visualize links between Jira issues as dependency lines:

User Story Map with dependency lines.png

The app will show dependencies between standard-level issues, including Stories, Tasks and Bugs. Dependencies with sub-tasks and Epics aren’t currently displayed.

Dependency links will only show where both of the linked issues are on the User Story Map.

Switching on dependency lines

Open the “Dependencies” dropdown in the User Story Map header to switch on dependency lines.

Dependencies dropdown in User Story Map header, with the Show dependencies option switched off

This is toggled off by default, but will remember how you last set it. All the configuration selected in this dropdown will be saved for you, and won’t affect other users' views.

Color-coded dependency health

A dependency line shows which issue needs to be done first, and which issue is dependent on it and must be done second.

  • red line is shown when the second issue is scheduled before the first issue: this plan has a Conflict.

  • An orange line is shown when both issues are scheduled in the same sprint: this plan is At risk.

  • green line is shown when the issues are scheduled in the right sequence: this plan is Healthy.

You can switch dependency lines on and off based on health. For example, you might switch off Healthy dependencies so you can focus on resolving the At-risk and Conflict plans.

Toggling at risk dependency health on the User Story Map, showing an orange line appearing and disappearing

The Dependencies button in the app header shows:

  • What dependency health colors are currently switched on

  • The total number of dependencies which are visible with the current settings

Dependencies dropdown shows health, number.png

Select issue link types from Jira

Select which issue link types you’d like to display as dependency lines.

Dependency link types.png

This list will show the issue link types available in Jira, which will include:

  • Default issue link types like “Blocks (blocked / is blocked by)”

  • Any custom issue link types added to your Jira site

A Jira Administrator can configure what link types are available in your Jira site. Learn more in Atlassian’s documentation for Configuring issue linking on Jira Cloud.

Dependency details

When you hover over a dependency line, you’ll see an (info) Information icon. Click this to see the details of this dependency link.

Dependency line info icon.png
Dependency details popup.png

Creating and editing dependencies

The User Story Map will show dependency lines based on existing issue links. You can create or delete these in the Linked Issues section when viewing the issue in Jira:

The Linked issues section in the Jira Cloud issue view

Learn more with Atlassian’s guide on linking issues in Jira Cloud.

Click the issue key (eg. “ABC-123”) on any issue in Easy Agile TeamRhythm to quickly open the Jira Cloud issue view.

Can’t see dependencies?

If you can view and create issue links in Jira, but they’re missing on the User Story Map:

  • Check if you’re Jira Cloud, or Jira Data Center / Server. On Jira Cloud, the page URL will always have “.atlassian.net”. Dependency lines are currently only available when using the app on Jira Cloud.

  • Check what filters are switched on in the Dependencies dropdown.

    • Try switching on all Health types (Healthy, At risk, Conflict).

    • Check that the issue link type named on the Jira issue is checked in the “Types”.

  • Check that both of the issues are currently visible on the User Story Map.

If you can’t see or create issue links in Jira, contact your Jira Administrator or internal IT support team.

  • A Jira Administrator can enable or disable issue linking for the whole Jira site. See Atlassian’s guide to Configure issue linking.

  • The “Linked issues” field might be hidden on the Issue Screen. This doesn’t stop the “Linked issues” section showing in the Jira issue view, but does prevent apps like Easy Agile TeamRhythm from loading issue link data.

  • To create new issue links, you’ll need the “Link Issues” permission. If the issues you want to link are from different Jira projects, you’ll need this permission for both projects. For company-managed Jira projects, this is configured in the Permissions Scheme selected for that project. A Jira Administrator can update these permissions.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.