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

You can:

Restrictions can be made via workflow conditions and validators (https://confluence.atlassian.com/display/JIRA/Advanced+workflow+configuration). There are also some plugins around, check which are available in the cloud.

 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

523 views 1 18
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