is there a structured way to identify dependencies between existing stories in jira?

Hi, if I have previously entered 2 separate stories in JIRA (Story A and Story B) then is there a way to configure Story B in a structured way so that it is clearly marked as a dependency of Story A?  In other words, Story B cannot be started until Story A is completed?  Furthermore, I'm wondering if other types of dependencies can be configured.  For example, start-to-start, finish-to-finish, etc.  Please let me know what Jira's capabilities are in this regard.

1 answer

This widget could not be displayed.

You can:

Restrictions can be made via workflow conditions and validators ( There are also some plugins around, check which are available in the cloud.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

172 views 1 3
Join discussion

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