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

[Andrew Ciccarelli]

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.

[Gabrielle Bautista [ACP-JA]]

You can:

• Use JIRA Links https://confluence.atlassian.com/display/JIRA/Linking+Issues
• Use Sub Tasks https://confluence.atlassian.com/display/JIRA/Creating+a+Sub-Task

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.