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")
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
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events