How are dependencies done in JIRA Agile?

I am new to the products because I am performing an evaluation.  I apologize if I am user the wrong terms to describe my need.   I have a need to establish and track dependencies from a user story (US)in one project to another one in a different project.  We have many projects in flight at one time. 

Is there a demo / walk through that is available that will show me how this is done?

I saw some discussion about dependencies between Epics.  I want to focus on the US for now.

7 answers

Hi Jim,

JIRA may have the ability to extract this information, and there may be plug-ins that enable filters to obtain information on linked issues, release dates, and sprint end dates from JIRA.

Release dates are managed through fixVersions and we use a code name to designate a release.

Iterations and iteration end dates are managed through the Agile Boards; we use the Sprint identifier, e.g. ProjectNameSprint99 to signify the iteration. The team is aware of iteration start and end dates.

Story state is available from JIRA.

For an issue, project ABC, number 123: ABC-123 would be linked to ABC-144 (typically we used "blocked by" or "relates to" or "duplicates" which may be a customisation of the standard implemenation). It provides visibility of dependencies on an issue by issue basis.





"Blocked by" is too heavy a hammer for dependencies for us. For us it means "I'm working on a story in the current sprint and I'm blocked by ..." Similar to using a red "Blocked" label in Trello and tagging cards with it.

Dependencies describe an order in which things need to done.  At a minimum I want, when I try to drag a story (or task) x into a sprint and story x depends story y being "Done", I'm told that I can't do that before story y is done. And if I try to drag story y above story x in the backlog, I can't do that either. It's deviation from pure Agile where the relative order of cards in the Backlog is assumed to tell the whole story.

We'd be happy with "Depends on" as a type of issue link if it came along with "you can't do that" as described above.  We do think some about  dependencies when prioritizing the backlog up front before we start sprinting. 

Greg, How did you end up on this? We're you able to find a work around, add-on, or other solution? I am having a similar issue. We use MS Project and Jira but all my dependencies are in Jira at a story level, not at an Epic level. 

0 votes

Hi Jim,

I believe that you can take a look on this page from our documentation to accomplish this, as it details how to have a board showing stories from multiple projects (and, thus, creating some kind of dependency as you may note).

-- Arthur Gonçalves


Thank you for your response.  I was able to create a board that shows the US of both projects.

Is there a demo / walk through that show how to create the Dependency itself?



Hello Jim,

As a JIRA user, my team has used the "linking" feature to track dependencies. I too would be interested in more ways to track dependencies in JIRA.




Interesting, You use the "linking" feature now. 

Do you have something that shows the Predecessor and Successor on the same row.

Maybe something like this?

Predecessor ProjectPredecessor StoryStory StateRelease DateIteration End Date|||Successor ProjectSuccessor StoryStory StateRelease DateIteration End Date


Thank you for you information.  This was very helpful.



0 votes

Late to the conversation here, but in case others come along like I did.

We also need to indicate dependencies and found:

  1. an option to show dependencies via Portfolio
  2. the option to use Issue Linking

Issue linking does not have a dependencies option by default. So, we created one. You can do this by going to Settings (global, not project or board) -> Issue Linking -> Add New Link Type. We set it up as follows:

  1. Name = Dependent
  2. Outward Link Description = a dependent of
  3. Inward Link Description = is dependent on

I hope this helps someone else.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

572 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you