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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,826 views 12 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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot