JIRA will not enforce dependencies, but you can link records together with a type of "Depends on".
Also, you could create sub-tasks in a particular order, but again, JIRA will not enforce this, and if the person assigned to the sub-task doesn't look at the parent story or defect, they will not know the order.
You'll need to explain what you mean by "dependencies" (But the initial instinctive answer is "use issue links to record and show dependencies")
Cool, thanks guys that has helped me out.
Hi Nic, I have similar use case. My dependencies can be at any of this level (of the same type): Epic <-->Epic, Story <-->Story, Task <--->Task. Starting with Epic, I can't seem to find a way to describe this relationship: Epic2 depends on Epic1. Thoughts? Thanks
It looks like you're new here. Sign in or register to get started.
