What's the purpose of a work item Depends On link

I'm curious as to how people are using the Depends On link type in conjunction with an Agile project. I was hoping to two create two work items that are not parent/child, but which depend on each other. For example, work item A can't be completed work item B is completed. It appeared as though the Depends On link type would be perfect for this. Work item A Depends On work item B. Work item B therefore blocks work item A. I was hoping that I wouldn't be allowed to resolve work item A until work item B was resolved. However, in testing the behavior, this isn't the way it works.

So now I'm wondering why I would want to use a Depends On link. Also, does anyone know of a way to implement the scenario I described?

Hi,

The Depends on and Blocks link is a logical dependency and not a schedule dependency. The scheduling is not impacted by adding these dependencies which is why you do not see any restriction or errors/warnings when these dependencies are added.

Thanks,
Sharoon - Planning team

I'm curious as to how people are using the Depends On link type in conjunction with an Agile project. I was hoping to two create two work items that are not parent/child, but which depend on each other. For example, work item A can't be completed work item B is completed. It appeared as though the Depends On link type would be perfect for this. Work item A Depends On work item B. Work item B therefore blocks work item A. I was hoping that I wouldn't be allowed to resolve work item A until work item B was resolved. However, in testing the behavior, this isn't the way it works.

So now I'm wondering why I would want to use a Depends On link. Also, does anyone know of a way to implement the scenario I described?